Time domain resource allocation for mobile communication

ABSTRACT

Systems, apparatuses, methods, and computer-readable media are provided for time domain resource allocations in wireless communications systems. Disclosed embodiments include time-domain symbol determination and/or indication using a combination of higher layer and downlink control information signaling for physical downlink shared channel and physical uplink shared channel; time domain resource allocations for mini-slot operations; rules for postponing and dropping for multiple mini-slot transmission; and collision handling of sounding reference signals with semi-statically or semi-persistently configured uplink transmissions. Other embodiments may be described and/or claimed.

RELATED APPLICATIONS

The present application claims priority under 35 U.S.C. § 119 to U.S.Provisional App. No. 62/617,106 filed Jan. 12, 2018, U.S. ProvisionalApp. No. 62/618,477 filed Jan. 17, 2018, and U.S. Provisional App. No.62/620,185 filed Jan. 22, 2018, the contents of each of which are herebyincorporated by reference in their entireties.

FIELD

Various embodiments of the present application generally relate to thefield of wireless communications, and in particular, to time domainresource allocation for cellular communications.

BACKGROUND

Mobile communication has evolved significantly from early voice systemsto today's highly sophisticated integrated communication platform. Thenext generation wireless communication systems, 5G or NR, provide accessto information and sharing of data anywhere, anytime by various usersand applications. In general, NR is an evolution of the wirelessconnectivity solutions of 3GPP LTE-Advanced. NR is meant to enableeverything connected by wireless and deliver fast, rich content andservices. NR is expected to be a unified network/system that is targetedto meet vastly different and sometimes conflicting performancedimensions and services. Such diverse multi-dimensional requirements aredriven by different services and applications.

BRIEF DESCRIPTION OF THE FIGURES

FIG. 1 depicts an architecture of a system of a network in accordancewith some embodiments.

FIG. 2 depicts an architecture of a system including a first corenetwork in accordance with some embodiments.

FIG. 3 depicts an architecture of a system including a second corenetwork in accordance with some embodiments.

FIG. 4 depicts an example of infrastructure equipment in accordance withvarious embodiments.

FIG. 5 depicts example components of a computer platform in accordancewith various embodiments.

FIG. 6 depicts a block diagram illustrating components, according tosome example embodiments, able to read instructions from amachine-readable or computer-readable medium (e.g., a non-transitorymachine-readable storage medium) and perform any one or more of themethodologies discussed herein.

FIG. 7 depicts example components of baseband circuitry and radiofrequency circuitry in accordance with various embodiments.

FIG. 8 is an illustration of various protocol functions that may be usedfor various protocol stacks in accordance with various embodiments.

FIGS. 9-11 depict example processes for practicing the variousembodiments discussed herein. In particular,

FIG. 9 shows an example time domain table configuration process and anallocation table building process according to various embodiments;

FIG. 10 shows an example physical shared channel slot determinationprocess 1000 according to various embodiments; and

FIG. 11 shows an example time domain allocation configuration process1100 according to various embodiments.

DETAILED DESCRIPTION

Embodiments herein provide mechanisms for TDRA for DL and UL sharedchannels, for example, PDSCH and PUSCH, that may be scheduleddynamically using DCI carried by PDCCH or based on semi-staticconfigurations, for example, DL SPS or UL transmissions without ULgrant. In particular, the present disclosure discusses embodiments forindicating time-domain symbols using a combination of higher layer andDCI signaling for PDSCH and PUSCH, as well as handling of time-domainresource allocation fields and related signaling for fallback DCIformats (e.g., DCI formats 0_0 and 1_0). The present disclosure alsodiscusses embodiments related to TDRA for mini-slot operation includingembodiments related to postponing and/or dropping multi-slot and/ormini-slot transmissions. In particular, for PDSCH or PUSCH withaggregated slots wherein a transport block is repeated with the same ordifferent redundancy versions (RVs), the present disclosure discussesembodiments related to resource mapping for multiple slots withPDSCH/PUSCH mapping type A, and for multiple mini-slots with at leastlengths of 2, 4, 7 symbols with PDSCH/PUSCH mapping type B. The presentdisclosure also discusses embodiments related to conflict resolution forlink direction conflicts or collisions between physical channels. Inparticular, embodiments include collision handling of SRS withsemi-statically or semi-persistently configured UL transmission. Otherembodiments may be described and/or claimed.

Referring now to FIG. 1, in which an example architecture of a system100 of a network according to various embodiments, is illustrated. Thefollowing description is provided for an example system 100 thatoperates in conjunction with the LTE system standards and 5G or NRsystem standards as provided by 3GPP technical specifications. However,the example embodiments are not limited in this regard and the describedembodiments may apply to other networks that benefit from the principlesdescribed herein, such as future 3GPP systems (e.g., Sixth Generation(6G)) systems, IEEE 802.16 protocols (e.g., WMAN, WiMAX, etc.), or thelike.

As shown by FIG. 1, the system 100 includes UE 101 a and UE 101 b(collectively referred to as “UEs 101” or “UE 101”). In this example,UEs 101 are illustrated as smartphones (e.g., handheld touchscreenmobile computing devices connectable to one or more cellular networks),but may also comprise any mobile or non-mobile computing device, such asconsumer electronics devices, cellular phones, smartphones, featurephones, tablet computers, wearable computer devices, personal digitalassistants (PDAs), pagers, wireless handsets, desktop computers, laptopcomputers, in-vehicle infotainment (IVI), in-car entertainment (ICE)devices, an Instrument Cluster (IC), head-up display (HUD) devices,onboard diagnostic (OBD) devices, dashtop mobile equipment (DME), mobiledata terminals (MDTs), Electronic Engine Management System (EEMS),electronic/engine control units (ECUs), electronic/engine controlmodules (ECMs), embedded systems, microcontrollers, control modules,engine management systems (EMS), networked or “smart” appliances, MTCdevices, M2M, IoT devices, and/or the like. As discussed in more detailinfra, the UEs 101 incorporate the time domain resource allocationembodiments discussed herein. In these embodiments, the UEs 101 arecapable of determining symbols for time domain resource allocation(s)based on a combination of higher layer and downlink control informationsignaling for PDSCH and/or PUSCH; time domain resource allocation(s) formini-slot operations; rules for postponing and dropping for multiplemini-slot transmissions; and collision handling of SRSs withsemi-statically or semi-persistently configured UL transmissions.

In some embodiments, any of the UEs 101 may be IoT UEs, which maycomprise a network access layer designed for low-power IoT applicationsutilizing short-lived UE connections. An IoT UE can utilize technologiessuch as M2M or MTC for exchanging data with an MTC server or device viaa PLMN, ProSe or D2D communication, sensor networks, or IoT networks.The M2M or MTC exchange of data may be a machine-initiated exchange ofdata. An IoT network describes interconnecting IoT UEs, which mayinclude uniquely identifiable embedded computing devices (within theInternet infrastructure), with short-lived connections. The IoT UEs mayexecute background applications (e.g., keep-alive messages, statusupdates, etc.) to facilitate the connections of the IoT network.

The UEs 101 may be configured to connect, for example, communicativelycouple, with an or RAN 110. In embodiments, the RAN 110 may be an NG RANor a 5G RAN, an E-UTRAN, or a legacy RAN, such as a UTRAN or GERAN. Asused herein, the term “NG RAN” or the like refers to a RAN 110 thatoperates in an NR or 5G system 100, and the term “E-UTRAN” or the likerefers to a RAN 110 that operates in an LTE or 4G system 100. The UEs101 utilize connections (or channels) 103 and 104, respectively, each ofwhich comprises a physical communications interface or layer (discussedin further detail below).

In this example, the connections 103 and 104 are illustrated as an airinterface to enable communicative coupling, and can be consistent withcellular communications protocols, such as a GSM protocol, a CDMAnetwork protocol, a PTT protocol, a POC protocol, a UMTS protocol, a3GPP LTE protocol, a 5G protocol, a NR protocol, and/or any of the othercommunications protocols discussed herein. In embodiments, the UEs 101may directly exchange communication data via a ProSe interface 105. TheProSe interface 105 may alternatively be referred to as a SL interface105 and may comprise one or more logical channels, including but notlimited to a PSCCH, a PSSCH, a PSDCH, and a PSBCH.

The UE 101 b is shown to be configured to access an AP 106 (alsoreferred to as “WLAN node 106,” “WLAN 106,” “WLAN Termination 106,” “WT106” or the like) via connection 107. The connection 107 can comprise alocal wireless connection, such as a connection consistent with any IEEE802.11 protocol, wherein the AP 106 would comprise a WiFi® router. Inthis example, the AP 106 is shown to be connected to the Internetwithout connecting to the core network of the wireless system (describedin further detail below). In various embodiments, the UE 101 b, RAN 110,and AP 106 may be configured to utilize LWA operation and/or LWIPoperation. The LWA operation may involve the UE 101 b in RRC_CONNECTEDbeing configured by a RAN node 111 a-b to utilize radio resources of LTEand WLAN. LWIP operation may involve the UE 101 b using WLAN radioresources (e.g., connection 107) via IPsec protocol tunneling toauthenticate and encrypt packets (e.g., IP packets) sent over theconnection 107. IPsec tunneling may include encapsulating the entiretyof original IP packets and adding a new packet header, therebyprotecting the original header of the IP packets.

The RAN 110 can include one or more AN nodes or RAN nodes 111 a and 111b (collectively referred to as “RAN nodes 111” or “RAN node 111”) thatenable the connections 103 and 104. As used herein, the terms “accessnode,” “access point,” or the like may describe equipment that providesthe radio baseband functions for data and/or voice connectivity betweena network and one or more users. These access nodes can be referred toas BS, gNBs, RAN nodes, eNBs, NodeBs, RSUs, TRxPs or TRPs, and so forth,and can comprise ground stations (e.g., terrestrial access points) orsatellite stations providing coverage within a geographic area (e.g., acell). As used herein, the term “NG RAN node” or the like refers to aRAN node 111 that operates in an NR or 5G system 100 (e.g., a gNB), andthe term “E-UTRAN node” or the like refers to a RAN node 111 thatoperates in an LTE or 4G system 100 (e.g., an eNB). According to variousembodiments, the RAN nodes 111 may be implemented as one or more of adedicated physical device such as a macrocell base station, and/or a lowpower (LP) base station for providing femtocells, picocells or otherlike cells having smaller coverage areas, smaller user capacity, orhigher bandwidth compared to macrocells.

In some embodiments, all or parts of the RAN nodes 111 may beimplemented as one or more software entities running on server computersas part of a virtual network, which may be referred to as a CRAN and/ora virtual baseband unit pool (vBBUP). In these embodiments, the CRAN orvBBUP may implement a RAN function split, such as a PDCP split whereinRRC and PDCP layers are operated by the CRAN/vBBUP and other L2 protocolentities are operated by individual RAN nodes 111; a MAC/PHY splitwherein RRC, PDCP, RLC, and MAC layers are operated by the CRAN/vBBUPand the PHY layer is operated by individual RAN nodes 111; or a “lowerPHY” split wherein RRC, PDCP, RLC, MAC layers and upper portions of thePHY layer are operated by the CRAN/vBBUP and lower portions of the PHYlayer are operated by individual RAN nodes 111. This virtualizedframework allows the freed-up processor cores of the RAN nodes 111 toperform other virtualized applications. In some implementations, anindividual RAN node 111 may represent individual gNB-DUs that areconnected to a gNB-CU via individual F 1 interfaces (not shown by FIG.1). In these implementations, the gNB-DUs may include one or more remoteradio heads or RFEMs (see, e.g., FIG. 4), and the gNB-CU may be operatedby a server that is located in the RAN 110 (not shown) or by a serverpool in a similar manner as the CRAN/vBBUP. Additionally oralternatively, one or more of the RAN nodes 111 may be next generationeNBs (ng-eNBs), which are RAN nodes that provide E-UTRA user plane andcontrol plane protocol terminations toward the UEs 101, and areconnected to a 5GC (e.g., CN 320 of FIG. 3) via an NG interface(discussed infra).

In V2X scenarios one or more of the RAN nodes 111 may be or act as RSUs.The term “Road Side Unit” or “RSU” refers to any transportationinfrastructure entity used for V2X communications. An RSU may beimplemented in or by a suitable RAN node or a stationary (or relativelystationary) UE, where an RSU implemented in or by a UE may be referredto as a “UE-type RSU,” an RSU implemented in or by an eNB may bereferred to as an “eNB-type RSU,” an RSU implemented in or by a gNB maybe referred to as a “gNB-type RSU,” and the like. In one example, an RSUis a computing device coupled with radio frequency circuitry located ona roadside that provides connectivity support to passing vehicle UEs 101(vUEs 101). The RSU may also include internal data storage circuitry tostore intersection map geometry, traffic statistics, media, as well asapplications/software to sense and control ongoing vehicular andpedestrian traffic. The RSU may operate on the 5.9 GHz Direct ShortRange Communications (DSRC) band to provide very low latencycommunications required for high speed events, such as crash avoidance,traffic warnings, and the like. Additionally or alternatively, the RSUmay operate on the cellular V2X band to provide the aforementioned lowlatency communications, as well as other cellular communicationsservices. Additionally or alternatively, the RSU may operate as a Wi-Fihotspot (2.4 GHz band) and/or provide connectivity to one or morecellular networks to provide uplink and downlink communications. Thecomputing device(s) and some or all of the radiofrequency circuitry ofthe RSU may be packaged in a weatherproof enclosure suitable for outdoorinstallation, and may include a network interface controller to providea wired connection (e.g., Ethernet) to a traffic signal controllerand/or a backhaul network.

Any of the RAN nodes 111 can terminate the air interface protocol andcan be the first point of contact for the UEs 101. In some embodiments,any of the RAN nodes 111 can fulfill various logical functions for theRAN 110 including, but not limited to, radio network controller (RNC)functions such as radio bearer management, uplink and downlink dynamicradio resource management and data packet scheduling, and mobilitymanagement.

In embodiments, the UEs 101 can be configured to communicate using OFDMcommunication signals with each other or with any of the RAN nodes 111over a multicarrier communication channel in accordance with variouscommunication techniques, such as, but not limited to, an OFDMAcommunication technique (e.g., for downlink communications) or a SC-FDMAcommunication technique (e.g., for uplink and ProSe or sidelinkcommunications), although the scope of the embodiments is not limited inthis respect. The OFDM signals can comprise a plurality of orthogonalsubcarriers.

Downlink and uplink transmissions may be organized into frames with 10ms durations, where each frame includes ten 1 ms subframes. A slotduration is 14 symbols with Normal CP and 12 symbols with Extended CP,and scales in time as a function of the used sub-carrier spacing so thatthere is always an integer number of slots in a subframe. In someembodiments, a downlink resource grid can be used for downlinktransmissions from any of the RAN nodes 111 to the UEs 101, while uplinktransmissions can utilize similar techniques. The grid can be atime-frequency grid, called a resource grid or time-frequency resourcegrid, which is the physical resource in the downlink in each slot. Sucha time-frequency plane representation is a common practice for OFDMsystems, which makes it intuitive for radio resource allocation. Eachcolumn and each row of the resource grid corresponds to one OFDM symboland one OFDM subcarrier, respectively. The duration of the resource gridin the time domain corresponds to one slot in a radio frame. Thesmallest time-frequency unit in a resource grid is denoted as a resourceelement. Each resource grid comprises a number of resource blocks, whichdescribe the mapping of certain physical channels to resource elements.Each resource block comprises a collection of resource elements; in thefrequency domain, this may represent the smallest quantity of resourcesthat currently can be allocated. There are several different physicaldownlink channels that are conveyed using such resource blocks.

The PDSCH carries user data and higher-layer signaling to the UEs 101.Typically, downlink scheduling (assigning control and shared channelresource blocks to the UE 101 b within a cell) may be performed at anyof the RAN nodes 111 based on channel quality information fed back fromany of the UEs 101. The downlink resource assignment information may besent on the PDCCH used for (e.g., assigned to) each of the UEs 101. ThePDCCH can be used to schedule DL transmissions on PDSCH and ULtransmissions on PUSCH, where the DCI on PDCCH includes, inter alia,downlink assignments containing at least modulation and coding format,resource allocation, and HARQ information related to DL-SCH; and/oruplink scheduling grants containing at least modulation and codingformat, resource allocation, and HARQ information related to UL-SCH. Inaddition to scheduling, the PDCCH can be used to for activation anddeactivation of configured PUSCH transmission with configured grant;activation and deactivation of PDSCH semi-persistent transmission;notifying one or more UEs 101 of a slot format; notifying one or moreUEs 101 of the PRB(s) and OFDM symbol(s) where a UE 101 may assume notransmission is intended for the UE; transmission of TPC commands forPUCCH and PUSCH; transmission of one or more TPC commands for SRStransmissions by one or more UEs; switching an active BWP for a UE 101;and initiating a random access procedure.

The PDCCH uses CCEs to convey the control information. Control channelsare formed by aggregation of one or more CCEs, where different coderates for the control channels are realized by aggregating differentnumbers of CCEs. Before being mapped to resource elements, the PDCCHcomplex-valued symbols may first be organized into quadruplets, whichmay then be permuted using a sub-block interleaver for rate matching.Each PDCCH is transmitted using one or more of these CCEs, where eachCCE may correspond to nine sets of four physical resource elements knownas REGs. Four QPSK symbols may be mapped to each REG. The PDCCH can betransmitted using one or more CCEs, depending on the size of the DCI andthe channel condition. For example, there can be four or more differentPDCCH formats defined in LTE with different numbers of CCEs (e.g.,aggregation level, L=1, 2, 4, or 8).

The UEs 101 monitor (or attempt to decode) respective sets of PDCCHcandidates in one or more configured monitoring occasions according tothe corresponding search space configurations. In NR implementations,the UEs 101 monitor (or attempt to decode) respective sets of PDCCHcandidates in one or more configured monitoring occasions in one or moreconfigured CORESETs according to the corresponding search spaceconfigurations. A CORESET includes a set of PRBs with a time duration of1 to 3 OFDM symbols. The REGs and CCEs are defined within a CORESET witheach CCE including a set of REGs. Interleaved and non-interleavedCCE-to-REG mapping are supported in a CORESET. Each REG carrying PDCCHcarries its own DMRS.

Some embodiments may use concepts for resource allocation for controlchannel information that are an extension of the above-describedconcepts. For example, some embodiments may utilize an EPDCCH that usesPDSCH resources for control information transmission. The EPDCCH may betransmitted using one or more ECCEs. Similar to above, each ECCE maycorrespond to nine sets of four physical resource elements known as anEREGs. An ECCE may have other numbers of EREGs in some situations.

The UEs 101, upon detection of a PDCCH with a configured DCI (e.g., DCIformat 1_0, DCI format 1_1, or some new DCI format) decode thecorresponding PDSCHs as indicated by that DCI. A closed loop DMRS basedspatial multiplexing is supported for PDSCH where up to 8 and 12orthogonal DL DMRS ports are supported for type 1 and type 2 DMRSrespectively. The UEs 101 may assume that at least one symbol with aDMRS is present on each layer in which a PDSCH is transmitted to a UE101, and up to three additional DMRSs can be configured by higherlayers. The DMRS and corresponding PDSCH are transmitted using the sameprecoding matrix and the UEs 101 do not need to know the precodingmatrix to demodulate the transmission. The transmitter (e.g., RAN node111) may use different precoder matrix for different parts of thetransmission bandwidth, resulting in frequency selective precoding. TheUEs 101 may also assume that the same precoding matrix is used across aset of PRBs denoted PRG.

When the UE 101 is scheduled to receive PDSCH by a DCI (e.g., DCI format1_0, DCI format 1_1, or a new DCI format), a time domain resourceassignment field value m of the DCI provides a row index m+1 to anallocation table. Depending on the DCI format, the time domain resourceassignment field maybe 4 bits, and in some cases, the bitwidth for thisfield is determined as ┌log₂(I)┐ bits, where I is the number of entriesin the higher layer parameter pdsch-TimeDomainAllocationList. Theindexed row defines a slot offset K₀, a start and length indicator SLIV(or directly the start symbol S and the allocation length L), and aPDSCH mapping type to be assumed in a PDSCH reception.

Given the parameter values of the indexed row the slot allocated for thePDSCH is

${\lfloor {n \cdot \frac{2^{\mu_{PDSCH}}}{2^{\mu_{PDCCH}}}} \rfloor + K_{0}},$

where n is the slot with the scheduling DCI, and K₀ is based on thenumerology of PDSCH, μ_(PDSCH) and μ_(PDCCH) are the subcarrier spacingconfigurations for PDSCH and PDCCH, respectively. The starting symbol Srelative to the start of the slot, and the number of consecutive symbolsL counting from the symbol S allocated for the PDSCH are determined fromthe start and length indicator SLIV: if (L−1)≤7 then SLIV=14·(L−1)+S,else SLIV=14·(14−L+1)+(14−1−S), where 0<L≤14−S. The PDSCH mapping typeis set to Type A or Type B is given by the index row. The PDSCH mappingtype (e.g., Type A or Type B) is related to the location/position of thecorresponding DMRS in the slot. For PDSCH mapping type A, a time domainsymbol for the DMRS is defined relative to the start of the slot,whereas for PDSCH mapping type B the time domain symbol for the DMRS isdefined relative to the starting symbol.

According to various embodiments, the UE 101 may consider the S and Lcombinations defined in table 1 as valid PDSCH allocations.

TABLE 1 Valid S and L combinations PDSCH Normal cyclic prefix Extendedcyclic prefix mapping type S L S + L S L S + L Type A {0, 1, 2, 3} {3, .. . , 14} {3, . . . , 14} {0, 1, 2, 3} {3, . . . , 12} {3, . . . , 12}(Note 1) (Note 1) Type B {0, . . . , 12} {2, 4, 7} {2, . . . , 14} {0, .. . , 10} {2, 4, 6} {2, . . . , 12} (Note 1) S = 3 is applicable only ifdmrs-TypeA-Posiition = 3

When the UE is configured with aggregationFactorDL>1, the same symbolallocation is applied across the aggregationFactorDL consecutive slots.The UE may expect that the TB is repeated within each symbol allocationamong each of the aggregationFactorDL consecutive slots and the PDSCH islimited to a single transmission layer. The redundancy version to beapplied on the n^(th) transmission occasion of the TB is determinedaccording to table 2.

TABLE 2 Applied redundancy version when aggregationFactorDL > 1 rv_(id)indicated by the DCI scheduling rv_(id) to be applied to n^(th)transmission occasion the PDSCH n mod 4 = 0 n mod 4 = 1 n mod 4 = 2 nmod 4 = 3 0 0 2 3 1 2 2 3 1 0 3 3 1 0 2 1 1 0 2 3

If the UE 101 procedure for determining slot configuration determinessymbol of a slot allocated for PDSCH as uplink symbols, the transmissionon that slot is omitted for multi-slot PDSCH transmission. The UE 101 isnot expected to receive a PDSCH with mapping type A in a slot, if thePDCCH scheduling the PDSCH was received in the same slot and was notcontained within the first three symbols of the slot. The UE 10 is notexpected to receive a PDSCH with mapping type B in a slot, if the firstsymbol of the PDCCH scheduling the PDSCH was received in a later symbolthan the first symbol indicated in the PDSCH time domain resourceallocation.

Table 3 defines which PDSCH time domain resource allocationconfiguration to apply. Either a default PDSCH time domain allocation A,B or C according to tables 4, 5, 6, and 7 is applied, or the higherlayer configured pdsch-TimeDomainAllocationList in eitherpdsch-ConfigCommon or pdsch-Config is applied.

TABLE 3 Applicable PDSCH time domain resource allocation SS/PBCH pdsch-block and ConfigCommon pdsch-Config PDCCH CORESET includes pdsch-includes pdsch- PDSCH time search multiplexing TimeDomainAllocationTimeDomainAllocation domain resource RNTI space pattern List Listallocation to apply SI-RNTI Type0 1 — — Default A for normal common CP 2— — Default B 3 — — Default C SI-RNTI Type0A 1 No — Default A common 2No — Default B 3 No — Default C 1, 2, 3 Yes — pdsch-TimeDomainAllocation List provided in pdsch- ConfigCommon RA-RNTI, Type11, 2, 3 No — Default A TC-RNTI common 1, 2, 3 Yes — pdsch-TimeDomainAllocation List provided in pdsch- ConfigCommon P-RNTI Type2 1No — Default A common 2 No — Default B 3 No — Default C 1, 2, 3 Yes —pdsch- TimeDomainAllocation List provided in pdsch- ConfigCommonC-RNTIMCS- Any common 1, 2, 3 No — Default A C-RNTI, CS- search 1, 2, 3Yes — pdsch- RNTI space TimeDomainAllocation associated List provided inwith pdsch- CORESET# 0 ConfigCommon C-RNTI, Any common 1, 2, 3 No NoDefault A MCS-C- search 1, 2, 3 Yes No pdsch- RNTI, CS- space notTimeDomainAllocation RNTI associated List provided in with pdsch-CORESET# 0 ConfigCommon UE specific 1, 2, 3 No/Yes Yes pdsch- searchTimeDomainAllocation space List provided in pdsch-Config

TABLE 4 Default PDSCH time domain resource allocation A for normal CPRow dmrs-TypeA- PDSCH index Position mapping type K₀ S L 1 2 Type A 0 212 3 Type A 0 3 11 2 2 Type A 0 2 10 3 Type A 0 3 9 3 2 Type A 0 2 9 3Type A 0 3 8 4 2 Type A 0 2 7 3 Type A 0 3 6 5 2 Type A 0 2 5 3 Type A 03 4 6 2 Type B 0 9 4 3 Type B 0 10 4 7 2 Type B 0 4 4 3 Type B 0 6 4 82, 3 Type B 0 5 7 9 2, 3 Type B 0 5 2 10 2, 3 Type B 0 9 2 11 2, 3 TypeB 0 12 2 12 2, 3 Type A 0 1 13 13 2, 3 Type A 0 1 6 14 2, 3 Type A 0 2 415 2, 3 Type B 0 4 7 16 2, 3 Type B 0 8 4

TABLE 5 Default PDSCH time domain resource allocation A for extended CPRow dmrs-TypeA- PDSCH index Position mapping type K₀ S L 1 2 Type A 0 26 3 Type A 0 3 5 2 2 Type A 0 2 10 3 Type A 0 3 9 3 2 Type A 0 2 9 3Type A 0 3 8 4 2 Type A 0 2 7 3 Type A 0 3 6 5 2 Type A 0 2 5 3 Type A 03 4 6 2 Type B 0 6 4 3 Type B 0 8 2 7 2 Type B 0 4 4 3 Type B 0 6 4 8 2,3 Type B 0 5 6 9 2, 3 Type B 0 5 2 10 2, 3 Type B 0 9 2 11 2, 3 Type B 010 2 12 2, 3 Type A 0 1 11 13 2, 3 Type A 0 1 6 14 2, 3 Type A 0 2 4 152, 3 Type B 0 4 6 16 2, 3 Type B 0 8 4

TABLE 6 Default PDSCH time domain resource allocation B dmrs-TypeA-PDSCH Row index Position mapping type K₀ S L  1 2, 3 Type B 0 2 2  2 2,3 Type B 0 4 2  3 2, 3 Type B 0 6 2  4 2, 3 Type B 0 8 2  5 2, 3 Type B0 10 2  6 2, 3 Type B 1 2 2  7 2, 3 Type B 1 4 2  8 2, 3 Type B 0 2 4  92, 3 Type B 0 4 4 10 2, 3 Type B 0 6 4 11 2, 3 Type B 0 8 4 12 (Note 1)2, 3 Type B 0 10 4 13 (Note 1) 2, 3 Type B 0 2 7 14 (Note 1) 2 Type A 02 12 3 Type A 0 3 11 15 2, 3 Type B 1 2 4 16 Reserved Note 1: If thePDSCH was scheduled with SI-RNTI in PDCCH Type0 common search space, theUE may assume that this PDSCH resource allocation is not applied

TABLE 7 Default PDSCH time domain resource allocation C dmrs-TypeA-PDSCH Row index Position mapping type K₀ S L  1 (Note 1) 2, 3 Type B 0 22  2 2, 3 Type B 0 4 2  3 2, 3 Type B 0 6 2  4 2, 3 Type B 0 8 2  5 2, 3Type B 0 10 2  6 Reserved  7 Reserved  8 2, 3 Type B 0 2 4  9 2, 3 TypeB 0 4 4 10 2, 3 Type B 0 6 4 11 2, 3 Type B 0 8 4 12 2, 3 Type B 0 10 413 (Note 1) 2, 3 Type B 0 2 7 14 (Note 1) 2 Type A 0 2 12 3 Type A 0 311 15 (Note 1) 2, 3 Type A 0 0 6 16 (Note 1) 2, 3 Type A 0 2 6 Note 1:The UE may assume that this PDSCH resource allocation is not used, ifthe PDSCH was scheduled with SI-RNTI in PDCCH Type0 common search space

PUSCH transmission(s) can be dynamically scheduled by an UL grant in aDCI, or semi-statically configured to operate upon the reception ofhigher layer parameter of configuredGrantConfig includingrrc-ConfiguredUplinkGrant without the detection of an UL grant in a DCI,or configurdGrantConfig not including rrc-ConfiguredUplinkGrantsemi-persistently scheduled by an UL grant in a DCI after the receptionof higher layer parameter configurdGrantConfig not includingrrc-ConfiguredUplinkGrant. A UE 101, upon detection of a PDCCH with aconfigured DCI (e.g., DCI format 0_0, DCI format 0_1, or the like),transmits the corresponding PUSCH as indicated by that DCI. For PUSCHscheduled by DCI format 0_0 on a cell, the UE 101 transmits the PUSCHaccording to a spatial relation corresponding to the PUCCH resource withthe lowest ID within the active UL BWP of the cell.

When the UE 101 is scheduled to transmit a transport block and no CSIreport, or the UE 101 is scheduled to transmit a transport block and aCSI report(s) on PUSCH by a DCI, the time domain resource assignmentfield value m of the DCI provides a row index m+1 to an allocated table.The indexed row defines the slot offset K₂, the start and lengthindicator SLIV, or directly the start symbol S and the allocation lengthL, and the PUSCH mapping type to be applied in the PUSCH transmission.

When the UE 101 is scheduled to transmit a PUSCH with no transport blockand with a CSI report(s) by a CSI request field on a DCI, theTime-domain resource assignment field value m of the DCI provides a rowindex m+1 to an allocated table which is defined by the higher layerconfigured pusch-TimeDomainAllocationList in pusch-Config. The indexedrow defines the start and length indicator SLIV, and the PUSCH mappingtype to be applied in the PUSCH transmission and the K₂ value isdetermined as

${K_{2} = {\max\limits_{j}{Y_{j}( {m + 1} )}}},$

where Y_(j), j=0, . . . , N_(Rep)−1 are the corresponding list entriesof the higher layer parameter reportSlotOffsetList in CSI-ReportConfigfor the N_(Rep) triggered CSI Reporting Settings and Y_(j)(m+1) is the(m+1)th entry of Y_(j).

The slot where the UE 101 transmits the PUSCH is determined by K₂ as

$\lfloor {n \cdot \frac{2^{\mu_{PUSCH}}}{2^{\mu_{PDCCH}}}} \rfloor + K_{2}$

where n is the slot with the scheduling DCI, K₂ is based on thenumerology of PUSCH, and μ_(PUSCH) and μ_(PDCCH) are the subcarrierspacing configurations for PUSCH and PDCCH, respectively. The startingsymbol S relative to the start of the slot, and the number ofconsecutive symbols L counting from the symbol S allocated for the PUSCHare determined from the start and length indicator SLIV of the indexedrow: if (L−1)≤7 then SLIV=14·(L−1)+S, else SLIV=14·(14−L+1)+(14−1−S),where 0<L≤14−S. The PUSCH mapping type is set to Type A or Type B isgiven by the indexed row. The PUSCH mapping type (e.g., Type A or TypeB) is related to the location/position of the corresponding DMRS in theslot. For PUSCH mapping type A, a time domain symbol for the DMRS isdefined relative to the start of the slot, whereas for PUSCH mappingtype B the time domain symbol for the DMRS is defined relative to thestarting symbol. According to various embodiments, the UE 101 mayconsider the S and L combinations defined in table 8 as valid PUSCHallocations.

TABLE 8 Valid S and L combinations PUSCH Normal cyclic prefix Extendedcyclic prefix mapping type S L S + L S L S + L Type A 0 {4, . . . , 14}{4, . . . , 14} 0 {4, . . . , 12} {4, . . . , 12} Type B {0, . . . , 13}{1, . . . , 14} {1, . . . , 14} {0, . . . , 12} {1, . . . , 12} {1, . .. , 12}

When the UE is configured with aggregationFactorUL>1, the same symbolallocation is applied across the aggregationFactorUL consecutive slotsand the PUSCH is limited to a single transmission layer. The UE 101repeats the TB across the aggregationFactorUL consecutive slots applyingthe same symbol allocation in each slot. The redundancy version to beapplied on the n^(th) transmission occasion of the TB is determinedaccording to table 9.

TABLE 9 Redundancy version when aggregationFactorUL > 1 rv_(id)indicated by the DCI scheduling rv_(id) to be applied to n^(th)transmission occasion the PUSCH n mod 4 = 0 n mod 4 = 1 n mod 4 = 2 nmod 4 = 3 0 0 2 3 1 2 2 3 1 0 3 3 1 0 2 1 1 0 2 3

If the UE 101 procedure for determining slot configuration determinessymbols of a slot allocated for PUSCH as downlink symbols, thetransmission on that slot is omitted for multi-slot PUSCH transmission.

Table 10 defines which PUSCH time domain resource allocationconfiguration to apply. Either a default PUSCH time domain allocation Aaccording to table 11, is applied, or the higher layer configuredpusch-TimeDomainAllocationList in either pusch-ConfigCommon orpusch-Config is applied. Table 13 defines the subcarrier spacingspecific values j. j is used in determination of K₂ in conjunction withtable 11 for normal CP or table 12 for extended CP, where μ_(PUSCH) isthe subcarrier spacing configurations for PUSCH. Table 14 defines theadditional subcarrier spacing specific slot delay value for the firsttransmission of for MSG3 scheduled by the RAR. When the UE transmits aMSG3 scheduled by RAR, the Δ value specific to MSG3 subcarrier spacingμ_(PUSCH) is applied in addition to the K₂ value.

TABLE 10 Applicable PUSCH time domain resource allocation PDCCHpusch-ConfigCommon pusch-Config includes search includes pusch- pusch-PUSCH time domain RNTI space TimeDomainAllocationListTimeDomainAllocationList resource allocation to apply PUSCH scheduled byNo — Default A MAC RAR Yes pusch- TimeDomainAllocationList provided inpusch- ConfigCommon C-RNTI, Any common No — Default A MCS-C- searchspace Yes pusch- RNTI, associated TimeDomainAllocationList TC- withprovided in pusch- RNTI, CORESET 0 ConfigCommon CS-RNTI C-RNTI, Anycommon No No Default A MCS-C- search space Yes No pusch- RNTI, notTimeDomainAllocationList TC- associated provided in pusch- RNTI, withConfigCommon CS-RNTI CORESET 0, No/Yes Yes pusch- UE specificTimeDomainAllocationList search space provided in pusch-Config

TABLE 11 Default PUSCH time domain resource allocation A for normal CPPUSCH Row index mapping type K₂ S L 1 Type A j 0 14 2 Type A j 0 12 3Type A j 0 10 4 Type B j 2 10 5 Type B j 4 10 6 Type B j 4 8 7 Type B j4 6 8 Type A j + 1 0 14 9 Type A j + 1 0 12 10 Type A j + 1 0 10 11 TypeA j + 2 0 14 12 Type A j + 2 0 12 13 Type A j + 2 0 10 14 Type B j 8 615 Type A j + 3 0 14 16 Type A j + 3 0 10

TABLE 12 Default PUSCH time domain resource allocation A for extended CPPUSCH Row index mapping type K₂ S L 1 Type A j 0 8 2 Type A j 0 12 3Type A j 0 10 4 Type B j 2 10 5 Type B j 4 4 6 Type B j 4 8 7 Type B j 46 8 Type A j + 1 0 8 9 Type A j + 1 0 12 10 Type A j + 1 0 10 11 Type Aj + 2 0 6 12 Type A j + 2 0 12 13 Type A j + 2 0 10 14 Type B j 8 4 15Type A j + 3 0 8 16 Type A j + 3 0 10

TABLE 13 Definition of value j μ_(PUSCH) j 0 1 1 1 2 2 3 3

TABLE 14 Definition of value Δ μ_(PUSCH) Δ 0 2 1 3 2 4 3 6

For the purposes of the present disclosure, it is assumed that theallocated PDSCH/PUSCH symbols are contiguous in time. With respect tothe time domain allocation for PDSCH and/or PUSCH, each row of a timedomain resource allocation table may be configured by higher layersignaling (e.g., RRC), where at least one table is configured for UL,and at least one table is configured for DL. Each time domain resourceallocation table may have up to 16 rows, and each row in a time domainresource allocation table is configured by RRC with a slot offset K₀field using 2 bits (for DL table) or a slot offset K₂ field using 3 bits(for UL table), an index (6 bit) into a table/equation capturing validcombinations of start symbol and length (which is jointly encoded), anda PDSCH mapping type field indicating whether type A or type B matchingtypes are applicable. The reference point for starting OFDM symbolshould have no RRC impact (e.g., slot boundary, start of CORESET wherethe PDCCH was found, or part of the table/equation). Additionally, anaggregation factor (1, 2, 4, 8 for DL or UL) is semi-staticallyconfigured separately and is not part of the table, which should havelittle to no additional RRC impact on how to use the aggregation factoralong with the tables.

While the aforementioned index uses 6 bits for this indication, 7 bitsmay be needed to convey the SLIV considering that there are 14 symbolsin a slot, and the SLIV jointly encodes the starting symbol and thelength of the PDSCH/PUSCH. Embodiments herein indicate the startingsymbol and length of PDSCH/PUSCH using no more than 6 bits of RRCsignaling. Aspects of such embodiments are based on the observation thatnot all combinations of starting symbols and lengths for PDSCH/PUSCH maybe supported for each of the mapping types (i.e., PDSCH/PUSCH mappingtypes A and B).

According to various embodiments, the following constraints may beapplied for PDSCH/PUSCH mapping type A: the indicated starting symbolmay only be one of symbols #0, 1, 2, 3; and the indicated length of thePDSCH/PUSCH is at least L_min, with L_min being no less than 2 symbolsand with a maximum of 14 symbols. In an example, L_min=3, or, in anotherexample, L_min=7. According to various embodiments, the followingconstraints may be applied for PDSCH/PUSCH mapping type B: the indicatedlength of the PDSCH/PUSCH can be one of 2, 4, or 7 symbols, and/or theindicated length of the PDSCH/PUSCH can be one of 1, 2, 4, or 7 symbols.

As mentioned previously, the rows of the time domain resource allocationtable are configured using semi-static RRC signaling, via the signalingof the following components by higher layers: slot offset indication (K₀using 2 bits for DL table or K₂ using 3 bits for UL table); a (row)index using 6 bits into a table/equation capturing valid combinations ofstart symbol and length (jointly encoded); and a PDSCH/PUSCH mappingtype of type A or type B.

In an embodiment, the starting symbol and length of the PDSCH/PUSCH fora row of the RRC configured table is determined as a function of thePDSCH/PUSCH mapping type for that row. In an embodiment, the slot offsetindication (K₀ and K₂ values) for a row of the RRC-configured table isdetermined as a function of the PDSCH/PUSCH mapping type for that row.In an embodiment, when PDSCH/PUSCH mapping type is A, a default table(e.g., one of the tables mentioned above) is used instead of an SLIVbased formulation such that all combinations of the following aresupported: starting symbol of 0, 1, 2, or 3 and allocation lengthbetween 7 through 14 symbols (alternative A1), or starting symbol of 0,1, 2, or 3 and allocation length between 3 and 14 symbols (alternativeA2). For mapping type A, alternative A1 may require 4 states each forlengths 7-10, and 1, 2, 3, and 4 states respectively for lengths 14, 13,12, 11, resulting in a total of 26 states. For alternative A2, thisbecomes 26 states+4*4 states=42 states.

In an embodiment, when PDSCH/PUSCH mapping type is B, a default tablethat is different from the one for PDSCH/PUSCH mapping type A is usedinstead of an SLIV based formulation such that all combinations of thefollowing are supported: all possible starting locations within a slotare possible for the allocation length of 2, 4, or 7 symbols such thatthe allocated symbols do not cross the slot-boundary (alternative B1),or all possible starting locations within a slot are possible for theallocation length of 1, 2, 4, or 7 symbols such that the allocatedsymbols do not cross the slot-boundary (alternative B2). For mappingtype B, alternative B1 may require 13, 11, and 8 states respectively forlengths 2, 4, and 7 symbols for a total of 32 states. For alternativeB2, this becomes 32 states+14 states=46 states.

In an embodiment for alternatives A1 and B1, a 5-bit or 6-bit table isdefined for each of mapping types A and B to indicate the candidatecombinations of starting symbols and length of the PDSCH/PUSCH toconstruct the RRC configured table. In this embodiment, the UE 101 usesthe appropriate table based on the 1 bit PDSCH/PUSCH mapping typeindicator to determine the starting symbol and length informationcorresponding to a row to build the RRC table. If a 6 bit table is used,the unused states are reserved.

Further, in an embodiment, for PDSCH mapping type B, the possible validvalues of K₀ are limited to only one of two values: 0 or 1. Additionallyor alternatively, in an embodiment, for PUSCH mapping type B, thepossible valid values of K₂ are limited to only one of two or fourvalues instead of eight values (corresponding to 3-bit for K₂).Additionally or alternatively, in an embodiment, when fallback DCIformats (formats 0_0 and 1_0) are used, the number of bits of thetime-domain RA field is reduced from 4 to 2 bits. To help facilitatesuch reduction, the candidate values for K₀, K₂ could be reduced toeffectively 0 or 1 bit, i.e., either a fixed value or one of two values.

For any of the embodiments discussed herein, it is assumed that thereference point for the starting symbol for the PDSCH/PUSCH is withrespect to the slot-boundary. This concept can be straightforwardlyapplied if the reference point for the starting symbol is with respectto the start of CORESET where the PDCCH was found.

In another embodiment, for PDSCH/PUSCH mapping type B, the reference isthe start of CORESET where the PDCCH was found, while for mapping typeA, the reference is slot boundary. In such a case, for PDSCH mappingtype B, under the assumption that the scheduled PDSCH may only bescheduled within the same slot where the PDCCH was found (i.e., K₀=0),the starting symbols of PDSCH may only be such that the resulting symbolindex is greater than the symbol index of the CORESET where the PDCCHwas found and less than #13. Without the K0=0 constraint, the tablespecified for mapping type B would indicate negative values when thestart of the CORESET is different from symbol #0.

There may be cases wherein lengths other than 2, 4, 7 symbols may needto be supported for mapping type B, for example, for PUSCH mapping typeB. In such cases, the table based approach to jointly indicate startingsymbol and length may require more than 6 bits. In such cases, insteadof using separate bit-fields to indicate the mapping type and the startand length values, these could be jointly encoded as a single fieldsignaled via higher layers to the UE 101. As can be seen from thediscussion infra, this can exploit the fact that for each mapping type Aor B, the number of valid states for starting symbol and length need notbe the same. Therefore, in an embodiment, the PDSCH/PUSCH mapping typeand PDSCH/PUSCH starting symbol and length indications are jointlyencoded. Such an approach can provide significantly increasedflexibility in time domain resource allocation while still limiting thetotal number of bits for signaling of the PDSCH/PUSCH mapping type andstarting symbol and length to 7 bits.

As mentioned previously, separate tables are configured for DL (PDSCH)and UL (PUSCH) from which the DCI bit-field indicates the resourceallocation. This means that different tables can be specified for DL andUL, respectively, with no more than 128 rows to jointly encode thePDSCH/PUSCH mapping types and the starting symbols and lengths for thePDSCH/PUSCH. Then the overall time-domain RA field can be built usinghigher layer signaling of K₀ or K₂ values and the 7 bit parameter thatjointly encodes the set of PDSCH/PUSCH mapping types and the startingsymbols and lengths for the PDSCH/PUSCH.

With this framework, the possible combinations for PDSCH and PUSCHregarding the starting symbol (S) and allocation length (L) and theresulting number of states that would need to be supported is shown bytable 15 and table 16, respectively. The selection of the ranges for Sand L for each mapping type and DL vs. UL channels shown by table 14follows the existing decisions in 3GPP on characteristics of eachmapping type in terms of relative location of the first occurring DMRSsymbol, the shared channel type (PDSCH or PUSCH), and correspondingexplicit or derived constraints on starting symbol and lengths.

TABLE 15 PDSCH starting symbol and allocation length combinations OptionMapping Type starting symbol (S) allocation length (L) Number of StatesDL_A1 mapping type A {0, 1, 2, 3} 7 to 14 symbols 26 DL_A2 mapping typeA {0, 1, 2, 3} 4 to 14 symbols 42 DL_B1 mapping type B 0 to 14 dependingon the 2, 4, 7 symbols 32 length such that the allocation does not crossthe slot boundary DL_B2 mapping type B 0 to 14 depending on the 1, 2, 4,7 symbols 46 length such that the allocation does not cross the slotboundary DL_B3 mapping type B 0 to 14 depending on the 1 to 7 symbols 77length such that the allocation does not cross the slot boundary DL_B4mapping type B 0 to 14 depending on the 1 to 13 symbols 104 length suchthat the allocation does not cross the slot boundary DL_B5 mapping typeB 0 to 14 depending on the 1 to 14 symbols 105 length such that theallocation does not cross the slot boundary

TABLE 16 PUSCH starting symbol and allocation length combinations OptionMapping Type starting symbol (S) allocation length (L) Number of StatesUL_A1 mapping type A 0 7 to 14 symbols 11 UL_A2 mapping type A 0 1 to 14symbols 14 UL_A3 mapping type A {0, 2, 3} 7 to 14 symbols 14 (S = 0), 7to 12 symbols (S = 2), 7 to 11 symbols (S = 3) UL_B1 mapping type B S =0 to 14 depending on 2, 4, 7 symbols 32 the length such that theallocation does not cross the slot boundary UL_B2 mapping type B 1 to 14depending on the 1 to 13 symbols 104 length such that the allocationdoes not cross the slot boundary UL_B3 mapping type B 0 to 14 dependingon the 1 to 14 symbols 105 length such that the allocation does notcross the slot boundary

Based on table 15, it can be seen that following the joint codingapproach, in order to remain within the 7 bit (maximum of 128 states)constraint, the following combinations of options can be supported:DL_B1 and either of DL_A1 or DL_A2; DL_B2 and either of DL_A1 or DL_A2;or DL_B3 and either of DL_A1 or DL_A2. To support option DL_B4 or DL_B5further compression, possibly using joint coding with the K₀ value canbe used. The feasibility of such an approach can be established based onthe fact that K₀ can be restricted to either 0 or 1 for PDSCH mappingtype B. Note that, although not necessary (as can be seen from analysisbelow), such joint encoding of all three parameters K₂, starting symbol& length, and the PUSCH mapping type can also be used for PUSCH to buildthe time-domain resource allocation table.

Based on table 16, it can be seen that following the joint codingapproach, in order to remain within the 7-bit (maximum of 128 states)constraint, the following combinations of options can be supported:UL_B1 and either of UL_A1, UL_A2, or UL_A3; UL_B2 and either of UL_A1,UL_A2, or UL_A3; and UL_B3 and either of UL_A1, UL_A2, or UL_A3. Notethat the DL and UL combinations can be selected independently as theyare signaled separately.

In terms of minimum UE 101 processing time (N2) for transmission ofPUSCH upon receiving an UL grant in the PDCCH, it has been agreed thatif data is mapped to the first symbol of the allocated PUSCH, eitherentirely or FDM-ed with PUSCH DMRS, an additional symbol is added to theN2 value for the corresponding subcarrier spacing (SCS). However, forPUSCH mapping type A, with PUSCH starting at symbol 0 of a slot, thereare two or three data-only symbols preceding the first location of thecorresponding PUSCH DMRS (symbol 2 or 3 of a slot). In such a case, theUE would have to prepare equivalent amount of data for mapping to thefirst two symbols before the PUSCH DMRS can be mapped (the latter can beprecomputed). Thus, in one embodiment, an additional k symbols are addedto the N2 value in case the PUSCH allocation is such that there are kdata-only symbols preceding the first occurrence of the PUSCH DMRS. Inanother embodiment, k=2 symbols are added to the N2 value for PUSCH withmapping type A with starting symbol 0 of a slot.

In another alternative embodiment can be to use the SLIV-based approachand use 7 bits to indicate the starting symbol and lengths, andseparately signal the K₀, K₂ and PDSCH/PUSCH mapping types. However, inthis case, to help the UE 101 implementation, in an embodiment, the UE101 does not expect to be scheduled with a time domain allocationcorresponding to certain combinations of starting symbols and lengths,and PDSCH/PUSCH mapping types. For PDSCH, the excluded combinations canbe identified as all combinations (e.g., 105 states for each mappingtype) other than the following sets: DL_B1 and either of DL_A1 or DL_A2;DL_B2 and either of DL_A1 or DL_A2; and/or DL_B3 and either of DL_A1 orDL_A2. For PUSCH, the excluded combinations can be identified as allcombinations (e.g., 105 states for each mapping type) other than thefollowing sets: UL_B1 and either of UL_A1 or UL_A_2 or UL_A3; UL_B_2 andeither of UL_A1 or UL_A2 or UL_A3; and UL_B_3 and either of UL_A1 orUL_A2 or UL_A3.

As mentioned previously, the PDSCH mapping type A corresponds to thecase wherein the first PDSCH DMRS occurs in the third or fourth symbol(e.g., symbol #2 or #3) of a slot. In these cases, for very short PDSCHdurations with PDSCH starting before the first PDSCH DMRS symbol, it canbe challenging for the UE 101 to meet tight processing time requirementsdue to the combined effect of delay in starting channel estimation forPDSCH demodulation late, and insufficient time in terms of the PDSCHduration for the decoding step to catch up to meet the processingtimeline. In an embodiment, for PDSCH mapping type A with PDSCHdurations of less than (or less than or equal to) seven symbols, oneadditional symbol is added to the N1 value for each PDSCH symbol thatoccurs before the first PDSCH DMRS, for both PDSCH processingcapabilities 1 and 2. In another embodiment, such additional time budgetto N1 for the case of PDSCH with mapping type A and duration less than(or less than or equal to) seven symbols is added only for PDSCHprocessing capability 2 and not for PDSCH processing capability 1. Inanother embodiment, the aforementioned consideration on additionalsymbols for each PDSCH symbol that occurs before the first PDSCH DMRSfor PDSCH mapping type A is applied for PDSCH durations less than orequal to four symbols.

According to various embodiments, the UE 101 may determine a time domainresource allocation indication for mini-slot operation. As mentionedpreviously, a DCI resource allocation field encodes the starting symboland duration (allocation length) of PDSCH/PUSCH transmission using aStart and Length Indication Value (SLIV) approach that jointly encodesthe starting symbol and duration (allocation length). This approachassumes a contiguous allocation of resources. Additionally, theaggregation factor of {1, 2, 4, 8} is configured semi-statically (e.g.,using RRC signaling). The aggregation factor is used to populate thetime-domain allocation over multiple slots or within a slot in order toorganize bundled and/or repeated transmission of a transport block.

In embodiments where slot-based resource allocation is used, such as forPDSCH/PUSCH mapping type A, if aggregation is configured, thedynamically indicated SLIV based resource allocation or semi-staticallyderived start and duration (in case of semi-persistent allocation) maybe assumed to be repeated in K consecutive valid slots, where K is theaggregation factor configured by RRC.

In embodiments where mini-slot based or non-slot based resourceallocation is used, such as for PDSCH/PUSCH mapping type B, ifaggregation is configured, the dynamically indicated SLIV based resourceallocation or semi-statically derived start and duration (in case ofsemi-persistent allocation) may be assumed to be repeated in consecutiveK groups of valid symbols, where K is the aggregation factor configuredby RRC. In these embodiments, the first group of valid symbols isdirectly derived from the time domain resource allocation fieldincluding SLIV indication which signals starting symbol and length insymbols. The other groups of symbols have the same length as the firstone and starting symbol index derived as the next valid symbol after theprevious group of symbols in an aggregation. In other words, themini-slots are repeated back-to-back without gaps within the validsymbols. For purposes of the present disclosure, the valid symbols aredefined as all symbols of a currently scheduled transmission direction,for example, DL for PDSCH and UL PUSCH. Further, PUSCH transmission caseis discussed in more detail infra, however, the aspects related to PUSCHtransmission are also applicable to PDSCH multi-slot and multi-mini-slottransmissions.

According to various embodiments, the UE 101 may determine or deriverules for postponing and/or dropping multi-mini-slot transmissions.Multi-mini-slot transmissions may lead to cases where a mini-slotcrosses a slot boundary and/or collides with at least scheduled SRStransmission(s). For such cases, dropping and/or postponing rules mayneed to be defined. In embodiments where a group of symbols in anaggregated multi-mini-slot transmission, such as aggregated PUSCHtransmission of mapping type B, is going to cross the slot boundary,such a transmission may need to be postponed. Postponing thetransmission may involve shifting in time to the first valid symbol in anext slot relative to the slot where the previous group of symbols wasmapped. For example, if a resource allocation (semi-static or dynamic)indicates starting symbol 7 (counting from 0) and a duration (allocationlength) of 4 symbols, while the aggregation factor is configured to 4,then the overall repeated resource allocation would be as shown by table17.

TABLE 17 N-th slot: --------00001111-- N + 1-th slot: 22223333----------

In another example, the groups of symbols that are determined to crossthe slot boundary and to be mapped to the next slots(s) are completelydropped as illustrated by table 18, which continues from the exampleshown by table 17.

TABLE 18 N-th slot: --------00001111-- N + 1-th slot: ------------------

In another example, the groups of symbols that are determined to crossthe slot boundary are dropped while the groups of symbols that aredetermined to be mapped to the next slot(s) are kept, as is shown bytable 19.

TABLE 19 N-th slot: --------00001111-- N + 1-th slot: --3333------------

In another embodiment, if the dynamic or semi-static time-domainresource allocation indicates resources which overlapped with SRSresources, the group(s) of PUSCH symbols fully or partially overlappedwith SRS resources are not transmitted. In this case, these PUSCHsymbols are either dropped or postponed. The same options as describedabove for the case of crossing slot boundary are applicable.Alternatively, the PUSCH transmission may be prioritized over the SRSresources and be transmitted instead. The prioritization rule may bebased on logical channel priority mapped to the corresponding PUSCH.E.g. the logical channel serving URLLC services may be prioritized overSRS transmissions.

According to various embodiments, the UE 101 may determine or derivepriority rules or dropping rules for handling collision (or potentialcollisions) between SRS and semi-statically or semi-persistentlyconfigured UL transmissions. The UE 101 can be configured with one ormore SRS resource sets as configured by the higher layer parameterSRS-ResourceSet. For each SRS resource set, the UE 101 may be configuredwith K≥1SRS resources via the higher layer parameter SRS-Resource, wherethe maximum value of K is indicated by the higher layer parameterSRS_capability. The SRS resource set applicability is configured by thehigher layer parameter usage in SRS-ResourceSet.

The UE 101 may apply priority rules or dropping rules when an SRScollides with a PUCCH with short duration. For example, the UE 101 maynot transmit SRS when semi-persistent and periodic SRS are configured inthe same symbol(s) with short PUCCH carrying only CSI reports, or ifaperiodic SRS is configured and short PUCCH consists of beam failurerequest. In the case that SRS is not transmitted due to overlap withshort PUCCH, only the SRS symbol(s) that overlap with short PUCCHsymbol(s) are dropped. The short PUCCH may not be transmitted whenaperiodic SRS happens to overlap in the same symbol with semi-persistentor periodic short PUCCH carrying semi-persistent/periodic CSI reportonly. Additionally, the UE 101 is not expected to be configured withaperiodic SRS and short PUCCH with aperiodic CSI report in the samesymbol. The UE 101 is not expected to be configured with SRS andPUSCH/UL DMRS/UL PTRS/Long PUCCH in the same symbol.

However, there are not any currently defined priority or dropping rulesfor SRS collisions with semi-statically or semi-persistently configuredUL transmissions, including Type 1 and Type 2 grant free ULtransmissions, UL semi-persistent transmissions, configured schedulinguplink transmissions, etc.

In one embodiment, the UE 101 does not transmit SRS when semi-persistentand periodic SRS are configured in the same symbol(s) with uplinktransmission which is semi-statically or semi-persistently configured.When the SRS is not transmitted due to overlap with uplink transmission,which is semi-statically or semi-persistently configured, only the SRSsymbol(s) that overlap with uplink transmission which is semi-staticallyor semi-persistently configured are dropped.

In another embodiment, the UE 101 does not transmit uplink transmissionwhich is semi-statically or semi-persistently configured when aperiodicSRS happens to overlap in the same symbol with transmit uplinktransmission which is semi-statically or semi-persistently configured.In another option, for type 2 UL transmission without grant, when thetransmission at the first activated resource collides with aperiodic SRStransmission, the aperiodic SRS transmission is dropped. For the uplinktransmission after the first activation, in case when UL transmissionwithout grant collides with aperiodic SRS transmission, UL transmissionwithout grant is dropped.

In another embodiment, when PRACH and physical uplink control channelcarrying beam failure request collide with uplink transmission, which issemi-statically or semi-persistently configured, the UE 101 does nottransmit uplink transmission which is semi-statically orsemi-persistently configured.

In another embodiment, the dropping rule or priority rule may depend ontransmission duration or type of uplink transmission. For instance, amini-slot based uplink transmission which is semi-statically orsemi-persistently configured may have higher priority than aperiodic SRStransmission, while a slot based uplink transmission, which issemi-statically or semi-persistently configured may have lower prioritythan the aperiodic SRS transmission.

Additionally or alternatively, the UE 101 does not transmit the SRS whensemi-persistent and periodic SRS are configured in the same symbol(s)with a PUCCH carrying only CSI report(s), or only L1-RSRP report(s).Additionally or alternatively, the UE 101 does not transmit SRS whensemi-persistent or periodic SRS is configured or aperiodic SRS istriggered to be transmitted in the same symbol(s) with PUCCH carryingHARQ-ACK and/or SR. In the case that SRS is not transmitted due tooverlap with PUCCH, only the SRS symbol(s) that overlap with PUCCHsymbol(s) are dropped. In these embodiments, the PUCCH should not betransmitted when aperiodic SRS is triggered to be transmitted to overlapin the same symbol with PUCCH carrying semi-persistent/periodic CSIreport(s) or semi-persistent/periodic L1-RSRP report(s) only. In case ofintra-band carrier aggregation or in inter-band CA band-band combinationwhere simultaneous SRS/PUCCH/PUSCH and PRACH transmissions are notallowed, the UE 101 is not expected to be configured with SRS andPUSCH/UL DM-RS/UL PT-RS/PUCCH in the same symbol.

According to various embodiments, the UE 101 may include mechanisms forsoft buffer handling. These soft buffer handling mechanisms are relatedto coding, multiplexing, and mapping transport channels and/or TBs tophysical channels. In general, data and control streams from/to the MAClayer are encoded/decoded to offer transport and control services overthe radio transmission link. The downlink physical-layer processing oftransport channels consists of the following steps: transport block CRCattachment; code block segmentation and code block CRC attachment;channel coding (e.g., LDPC coding); physical-layer HARQ processing; ratematching; scrambling; modulation (e.g., QPSK, 16QAM, 64QAM, and/or256QAM); layer mapping; and mapping to assigned resources and antennaports. The uplink physical-layer processing of transport channelsconsists of the following steps: transport Block CRC attachment; codeblock segmentation and Code Block CRC attachment; channel coding: LDPCcoding; physical-layer HARQ processing; rate matching; scrambling;modulation (e.g., it/2 BPSK (with transform precoding only), QPSK,16QAM, 64QAM and 256QAM); layer mapping, transform precoding (e.g.,enabled/disabled by configuration), and pre-coding; and mapping toassigned resources and antenna ports. A channel coding scheme is acombination of error detection, error correcting, rate matching,interleaving and transport channel or control information mappingonto/splitting from physical channels.

The soft buffer handling mechanisms enable the UE 101 to not perform astraight matching in the coding flow in the channel coding of the LDPCcode, and then go back all the way to the mother code rate. In general,the LDPC coding scheme involves encoding an input bit sequence denotedby c₀, c₁, c₂, c₃, . . . , c_(K-1), where K is the number of bits toencode; computing and attaching a CRC, which includes a number of paritybits generated by cyclic generator polynomials; and performingpuncturing, which is the process of removing some of the parity bitsafter encoding with the CRC. This process is performed in reverse fordecoding. The code rate for encoding the number of bits can be definedas a ratio of the data rate that is allocated for a subframe and themaximum data rate that ideally can be allocated in that subframe. Inother words, the code rate may be defined as the ratio between the TBSand the total number of physical layer bits per subframe that areavailable for transmission of that TB. A lower code rate means that moreredundancy bits are inserted during the channel coding process and ahigher code rate means that less redundancy bits are inserted.Sometimes, puncturing has a same or similar effect as encoding with anerror correction code with a higher rate, or less redundancy. Apunctured code may delete coded or redundant bits in a specific patternto adjust a code rate up from some lower “mother code” rate.

The number of bits to be encoded and decoded can sometimes be relativelylarge. When a relatively large number of bits are to be encoded, arelatively large number of bits may be punctured (thrown out) and nottransmitted, which may be the same or similar to a high code rateoperation. However, the decoder still needs to operate at a lower“mother” code rate when decoding the transmission. This means that thedecoder will have to handle a relatively large number of redundancybits, which increases complexity and taxes decoder throughput. Inembodiments, LBRM may be used to alleviate the demands on the decoder,wherein the decoder does not revert to the mother code rate. Instead,the decoder performs decoding at a code rate that is higher than themother code rate, but may be lower than the code rate used by theencoder. These embodiments enable more efficient decoder implementationsat the receivers.

In order to utilize the aforementioned LBRM embodiments, for each link(downlink or uplink), the corresponding parameters (e.g., maximum numberof layers supported by the UE 101 for the serving cell and maximummodulation order configured for the serving cell) for that link areused. For example, the downlink parameter settings are used for PDSCH,and uplink parameter settings are used for PUSCH. According to variousembodiments, when LBRM is applied, the downlink parameter settings arefor downlink TBs and the uplink parameter settings for uplink TBs.

Additionally, the UE 101 can support up to eight layers for downlink,where the maximum number of layers supported by the UE 101 for theserving cell is the maximum number of layers for one transport block. Invarious embodiments, such that LBRM is the maximum number of layerssupported by the UE for the serving cell for a TB such that LBRM isapplied based on four layers. This is because a TB cannot map to morethan four layers.

For example, the rate matching for LDPC code is defined per coded blockand includes bit selection and bit interleaving. The input bit sequenceto LDPC rate matching is d₀, d₁, d₂, . . . , d_(N-1), and the output bitsequence after rate matching is denoted as f₀, f₁, f₂, . . . , f_(E-1).Bit selection for LDPC rate matching includes writing an LDPC encodedbit sequence d₀, d₁, d₂, . . . , d_(N-1) into a circular buffer oflength N_(ch) for the r-th coded block, where N is a number of encodedbits, N=66Z_(c) for LDPC base graph 1 and N=50Z_(c) for LDPC base graph2, and Z_(c) is a minimum value in all sets of LDPC lifting size Z. Inthis example, for the r-th code block, N_(cb)=N if I_(LBRM)=0 andN_(cb)=min(N,N_(ref)) otherwise, where

${N_{ref} = \lfloor \frac{{TBS}_{LBRM}}{C \cdot R_{LBRM}} \rfloor},$

R_(LBRM)=2/3, TBS_(LBRM) is the LBRM transport block size for UL-SCH orthe LBRM transport block size for DL-SCH/PCH, assuming, inter alia, thatthe maximum number of layers for one TB supported by the UE 101 for theserving cell, which for UL-SCH is according to higher layer parameterULmaxRank if the parameter is configured; maximum modulation orderconfigured for the serving cell, if configured by higher layers;otherwise a maximum modulation order Q_(m)=6 is assumed for DL-SCH; amaximum coding rate of 948/1024; n_(PRB)=n_(PRB,LBRM), where the valueof n_(PRB,LBRM) for DL-SCH is determined according to the initialbandwidth part if there is no other bandwidth part configured to the UE;N_(RE)=156·n_(PRB); and c is a number of code blocks of the transportblock. n_(PRB,LBRM) is 32 when a maximum number of PRBs across allconfigured BWPs of a carrier is less than 33; 66 when the maximum numberof PRBs across all configured BWPs of a carrier is 33 to 66; 107 whenthe maximum number of PRBs across all configured BWPs of a carrier is 67to 107; 135 when the maximum number of PRBs across all configured BWPsof a carrier is 108 to 135; 162 when the maximum number of PRBs acrossall configured BWPs of a carrier is 136 to 162; 217 when the maximumnumber of PRBs across all configured BWPs of a carrier is 163 to 217; or273 when the maximum number of PRBs across all configured BWPs of acarrier is larger than 217.

In these embodiments, the soft buffer may be dimensioned so as to notrequire simultaneous support of peak rate, full IR support, and themaximum number of HARQ processes. In one example,Mlimit*(TBS_(LBRM)/R_(LBRM)) may be used as the number of soft bufferbits stored for a given CC. If the maximum number of HARQ processessupported for NR is 8 or 16, then M_(limit) can be a smaller value than8 or 16 (e.g., 4, may depend on N1 value) to reflect the UE storage isnot dimensioned for the simultaneous support of peak rate/full IR andmax HARQ processes.

Some concerns have been raised on applying very small value such as 2 msalways. On the other hand, from the perspective of the UE 101, it may bedesirable to not offer excessive soft buffer by using larger RTTs, suchas when the UE 101 supports relatively aggressive processing times,which may allow faster RTTs. In one embodiment, different reference RTTsare used for carriers in different frequency regions, where relativelyaggressive reference RTT numbers are used for scenarios where higherdata rates and faster RTTs are desired. In one example of suchembodiments includes: reference HARQ_RTT is [X] ms for frequencies below3 GHz and FR1, and a reference HARQ_RTT of [2] ms for 3-6 GHz and FR1.

The peak data rate formula can be adapted to include reference HARQ_RTTper component carrier to obtain the soft buffer dimensioning. An exampleof such a formula is shown by the following equation.

${SoftBuffer} = {\sum\limits_{j = 1}^{J}\; {( {v_{Layers}^{(j)} \cdot Q_{m}^{(j)} \cdot f^{(j)} \cdot R_{\max} \cdot \frac{N_{PRB}^{{{BW}{(j)}},\mu} \cdot 12}{T_{s}^{\mu}} \cdot ( {1 - {OH}^{(j)}} )} ) \cdot {refHARQRTT}^{(j)}}}$

Referring back to FIG. 1, the RAN nodes 111 may be configured tocommunicate with one another via interface 112. In embodiments where thesystem 100 is an LTE system (e.g., when CN 120 is an EPC 220 as in FIG.2), the interface 112 may be an X2 interface 112. The X2 interface maybe defined between two or more RAN nodes 111 (e.g., two or more eNBs andthe like) that connect to EPC 120, and/or between two eNBs connecting toEPC 120. In some implementations, the X2 interface may include an X2user plane interface (X2-U) and an X2 control plane interface (X2-C).The X2-U may provide flow control mechanisms for user data packetstransferred over the X2 interface, and may be used to communicateinformation about the delivery of user data between eNBs. For example,the X2-U may provide specific sequence number information for user datatransferred from a MeNB to an SeNB; information about successful insequence delivery of PDCP PDUs to a UE 101 from an SeNB for user data;information of PDCP PDUs that were not delivered to a UE 101;information about a current minimum desired buffer size at the SeNB fortransmitting to the UE user data; and the like. The X2-C may provideintra-LTE access mobility functionality, including context transfersfrom source to target eNBs, user plane transport control, etc.; loadmanagement functionality; as well as inter-cell interferencecoordination functionality.

In embodiments where the system 100 is a 5G or NR system (e.g., when CN120 is an 5GC 320 as in FIG. 3), the interface 112 may be an Xninterface 112. The Xn interface is defined between two or more RAN nodes111 (e.g., two or more gNBs and the like) that connect to 5GC 120,between a RAN node 111 (e.g., a gNB) connecting to 5GC 120 and an eNB,and/or between two eNBs connecting to 5GC 120. In some implementations,the Xn interface may include an Xn user plane (Xn-U) interface and an Xncontrol plane (Xn-C) interface. The Xn-U may provide non-guaranteeddelivery of user plane PDUs and support/provide data forwarding and flowcontrol functionality. The Xn-C may provide management and errorhandling functionality, functionality to manage the Xn-C interface;mobility support for UE 101 in a connected mode (e.g., CM-CONNECTED)including functionality to manage the UE mobility for connected modebetween one or more RAN nodes 111. The mobility support may includecontext transfer from an old (source) serving RAN node 111 to new(target) serving RAN node 111; and control of user plane tunnels betweenold (source) serving RAN node 111 to new (target) serving RAN node 111.A protocol stack of the Xn-U may include a transport network layer builton Internet Protocol (IP) transport layer, and a GTP-U layer on top of aUDP and/or IP layer(s) to carry user plane PDUs. The Xn-C protocol stackmay include an application layer signaling protocol (referred to as XnApplication Protocol (Xn-AP)) and a transport network layer that isbuilt on SCTP. The SCTP may be on top of an IP layer, and may providethe guaranteed delivery of application layer messages. In the transportIP layer, point-to-point transmission is used to deliver the signalingPDUs. In other implementations, the Xn-U protocol stack and/or the Xn-Cprotocol stack may be same or similar to the user plane and/or controlplane protocol stack(s) shown and described herein.

The RAN 110 is shown to be communicatively coupled to a core network—inthis embodiment, core network (CN) 120. The CN 120 may comprise aplurality of network elements 122, which are configured to offer variousdata and telecommunications services to customers/subscribers (e.g.,users of UEs 101) who are connected to the CN 120 via the RAN 110. Thecomponents of the CN 120 may be implemented in one physical node orseparate physical nodes including components to read and executeinstructions from a machine-readable or computer-readable medium (e.g.,a non-transitory machine-readable storage medium). In some embodiments,NFV may be utilized to virtualize any or all of the above-describednetwork node functions via executable instructions stored in one or morecomputer-readable storage mediums (described in further detail below). Alogical instantiation of the CN 120 may be referred to as a networkslice, and a logical instantiation of a portion of the CN 120 may bereferred to as a network sub-slice. NFV architectures andinfrastructures may be used to virtualize one or more network functions,alternatively performed by proprietary hardware, onto physical resourcescomprising a combination of industry-standard server hardware, storagehardware, or switches. In other words, NFV systems can be used toexecute virtual or reconfigurable implementations of one or more EPCcomponents/functions.

The CN 120 includes one or more servers 122, which may implement variouscore network elements or application functions (AFs) such as thosediscussed herein. The CN 120 is shown to be communicatively coupled toapplication servers 130 via an IP communications interface 125. Theapplication server(s) 130 comprise one or more physical and/orvirtualized systems for providing functionality (or services) to one ormore clients (e.g., UEs 101) over a network (e.g., network 150). Theserver(s) 130 may include various computer devices with rack computingarchitecture component(s), tower computing architecture component(s),blade computing architecture component(s), and/or the like. Theserver(s) 130 may represent a cluster of servers, a server farm, a cloudcomputing service, or other grouping or pool of servers, which may belocated in one or more datacenters. The server(s) 130 may also beconnected to, or otherwise associated with one or more data storagedevices (not shown). Moreover, the server(s) 130 may include anoperating system (OS) that provides executable program instructions forthe general administration and operation of the individual servercomputer devices, and may include a computer-readable medium storinginstructions that, when executed by a processor of the servers, mayallow the servers to perform their intended functions. Suitableimplementations for the OS and general functionality of servers areknown or commercially available, and are readily implemented by personshaving ordinary skill in the art. Generally, the server(s) 130 offerapplications or services that use IP/network resources. As examples, theserver(s) 130 may provide traffic management services, cloud analytics,content streaming services, immersive gaming experiences, socialnetworking and/or microblogging services, and/or other like services. Inaddition, the various services provided by the server(s) 130 may includeinitiating and controlling software and/or firmware updates forapplications or individual components implemented by the UEs 101. Theserver(s) 130 can also be configured to support one or morecommunication services (e.g., Voice-over-Internet Protocol (VoIP)sessions, PTT sessions, group communication sessions, social networkingservices, etc.) for the UEs 101 via the CN 120.

In embodiments, the CN 120 may be a 5GC (referred to as “5GC 120” or thelike), and the RAN 110 may be connected with the CN 120 via an NGinterface 113. In embodiments, the NG interface 113 may be split intotwo parts, an NG user plane (NG-U) interface 114, which carries trafficdata between the RAN nodes 111 and a UPF, and the S1 control plane(NG-C) interface 115, which is a signaling interface between the RANnodes 111 and AMFs. Embodiments where the CN 120 is a 5GC 120 arediscussed in more detail with regard to FIG. 3.

In embodiments, the CN 120 may be a 5G CN (referred to as “5GC 120” orthe like), while in other embodiments, the CN 120 may be an EPC). WhereCN 120 is an EPC (referred to as “EPC 120” or the like), the RAN 110 maybe connected with the CN 120 via an S1 interface 113. In embodiments,the S1 interface 113 may be split into two parts, an S1 user plane(S1-U) interface 114, which carries traffic data between the RAN nodes111 and the S-GW, and the S1-MME interface 115, which is a signalinginterface between the RAN nodes 111 and MMEs. An example architecturewherein the CN 120 is an EPC 120 is shown by FIG. 2.

FIG. 2 illustrates an example architecture of a system 200 including afirst CN 220, in accordance with various embodiments. In this example,system 200 may implement the LTE standard wherein the CN 220 is an EPC220 that corresponds with CN 120 of FIG. 1. Additionally, the UE 201 maybe the same or similar as the UEs 101 of FIG. 1, and the E-UTRAN 210 maybe a RAN that is the same or similar to the RAN 110 of FIG. 1, and whichmay include RAN nodes 111 discussed previously. The CN 220 may compriseMMEs 221, an S-GW 222, a P-GW 223, a HSS 224, and a SGSN 225.

The MMEs 221 may be similar in function to the control plane of legacySGSN, and may implement MM functions to keep track of the currentlocation of a UE 201. The MMEs 221 may perform various MM procedures tomanage mobility aspects in access such as gateway selection and trackingarea list management. MM (also referred to as “EPS MM” or “EMM” inE-UTRAN systems) refers to all applicable procedures, methods, datastorage, etc. that are used to maintain knowledge about a presentlocation of the UE 201, provide user identity confidentiality, and/orperform other like services to users/subscribers. Each UE 201 and theMME 221 may include an MM or EMM sublayer, and an MM context may beestablished in the UE 201 and the MME 221 when an attach procedure issuccessfully completed. The MM context may be a data structure ordatabase object that stores MM-related information of the UE 201. TheMMEs 221 may be coupled with the HSS 224 via an S6a reference point,coupled with the SGSN 225 via an S3 reference point, and coupled withthe S-GW 222 via an S11 reference point.

The SGSN 225 may be a node that serves the UE 201 by tracking thelocation of an individual UE 201 and performing security functions. Inaddition, the SGSN 225 may perform Inter-EPC node signaling for mobilitybetween 2G/3G and E-UTRAN 3GPP access networks; PDN and S-GW selectionas specified by the MMES 221; handling of UE 201 time zone functions asspecified by the MMES 221; and MME selection for handovers to E-UTRAN3GPP access network. The S3 reference point between the MMES 221 and theSGSN 225 may enable user and bearer information exchange for inter-3GPPaccess network mobility in idle and/or active states.

The HSS 224 may comprise a database for network users, includingsubscription-related information to support the network entities'handling of communication sessions. The EPC 220 may comprise one orseveral HSSs 224, depending on the number of mobile subscribers, on thecapacity of the equipment, on the organization of the network, etc. Forexample, the HSS 224 can provide support for routing/roaming,authentication, authorization, naming/addressing resolution, locationdependencies, etc. An S6a reference point between the HSS 224 and theMMES 221 may enable transfer of subscription and authentication data forauthenticating/authorizing user access to the EPC 220 between HSS 224and the MMES 221.

The S-GW 222 may terminate the S1 interface 113 (“S1-U” in FIG. 2)toward the RAN 210, and routes data packets between the RAN 210 and theEPC 220. In addition, the S-GW 222 may be a local mobility anchor pointfor inter-RAN node handovers and also may provide an anchor forinter-3GPP mobility. Other responsibilities may include lawfulintercept, charging, and some policy enforcement. The S11 referencepoint between the S-GW 222 and the MMES 221 may provide a control planebetween the MMES 221 and the S-GW 222. The S-GW 222 may be coupled withthe P-GW 223 via an S5 reference point.

The P-GW 223 may terminate an SGi interface toward a PDN 230. The P-GW223 may route data packets between the EPC 220 and external networkssuch as a network including the application server 130 (alternativelyreferred to as an “AF”) via an IP interface 125 (see e.g., FIG. 1). Inembodiments, the P-GW 223 may be communicatively coupled to anapplication server (application server 130 of FIG. 1 or PDN 230 in FIG.2) via an IP communications interface 125 (see, e.g., FIG. 1). The S5reference point between the P-GW 223 and the S-GW 222 may provide userplane tunneling and tunnel management between the P-GW 223 and the S-GW222. The S5 reference point may also be used for S-GW 222 relocation dueto UE 201 mobility and if the S-GW 222 needs to connect to anon-collocated P-GW 223 for the required PDN connectivity. The P-GW 223may further include a node for policy enforcement and charging datacollection (e.g., PCEF (not shown)). Additionally, the SGi referencepoint between the P-GW 223 and the packet data network (PDN) 230 may bean operator external public, a private PDN, or an intra operator packetdata network, for example, for provision of IMS services. The P-GW 223may be coupled with a PCRF 226 via a Gx reference point.

PCRF 226 is the policy and charging control element of the EPC 220. In anon-roaming scenario, there may be a single PCRF 226 in the Home PublicLand Mobile Network (HPLMN) associated with a UE 201's Internet ProtocolConnectivity Access Network (IP-CAN) session. In a roaming scenario withlocal breakout of traffic, there may be two PCRFs associated with a UE201's IP-CAN session, a Home PCRF (H-PCRF) within an HPLMN and a VisitedPCRF (V-PCRF) within a Visited Public Land Mobile Network (VPLMN). ThePCRF 226 may be communicatively coupled to the application server 230via the P-GW 223. The application server 230 may signal the PCRF 226 toindicate a new service flow and select the appropriate QoS and chargingparameters. The PCRF 226 may provision this rule into a PCEF (not shown)with the appropriate TFT and QCI, which commences the QoS and chargingas specified by the application server 230. The Gx reference pointbetween the PCRF 226 and the P-GW 223 may allow for the transfer of QoSpolicy and charging rules from the PCRF 226 to PCEF in the P-GW 223. AnRx reference point may reside between the PDN 230 (or “AF 230”) and thePCRF 226.

FIG. 3 illustrates an architecture of a system 300 including a second CN320 in accordance with various embodiments. The system 300 is shown toinclude a UE 301, which may be the same or similar to the UEs 101 and UE201 discussed previously; a (R)AN 310, which may be the same or similarto the RAN 110 and RAN 210 discussed previously, and which may includeRAN nodes 111 discussed previously; and a DN 303, which may be, forexample, operator services, Internet access or 3rd party services; and a5GC 320. The 5GC 320 may include an AUSF 322; an AMF 321; a SMF 324; aNEF 323; a PCF 326; a NRF 325; a UDM 327; an AF 328; a UPF 302; and aNSSF 329.

The UPF 302 may act as an anchor point for intra-RAT and inter-RATmobility, an external PDU session point of interconnect to DN 303, and abranching point to support multi-homed PDU session. The UPF 302 may alsoperform packet routing and forwarding, perform packet inspection,enforce the user plane part of policy rules, lawfully intercept packets(UP collection), perform traffic usage reporting, perform QoS handlingfor a user plane (e.g., packet filtering, gating, UL/DL rateenforcement), perform Uplink Traffic verification (e.g., SDF to QoS flowmapping), transport level packet marking in the uplink and downlink, andperform downlink packet buffering and downlink data notificationtriggering. UPF 302 may include an uplink classifier to support routingtraffic flows to a data network. The DN 303 may represent variousnetwork operator services, Internet access, or third party services. DN303 may include, or be similar to, application server 130 discussedpreviously. The UPF 302 may interact with the SMF 324 via an N4reference point between the SMF 324 and the UPF 302.

The AUSF 322 may store data for authentication of UE 301 and handleauthentication-related functionality. The AUSF 322 may facilitate acommon authentication framework for various access types. The AUSF 322may communicate with the AMF 321 via an N12 reference point between theAMF 321 and the AUSF 322; and may communicate with the UDM 327 via anN13 reference point between the UDM 327 and the AUSF 322. Additionally,the AUSF 322 may exhibit an Nausf service-based interface.

The AMF 321 may be responsible for registration management (e.g., forregistering UE 301, etc.), connection management, reachabilitymanagement, mobility management, and lawful interception of AMF-relatedevents, and access authentication and authorization. The AMF 321 may bea termination point for the an N11 reference point between the AMF 321and the SMF 324. The AMF 321 may provide transport for SM messagesbetween the UE 301 and the SMF 324, and act as a transparent proxy forrouting SM messages. AMF 321 may also provide transport for SMS messagesbetween UE 301 and an SMSF (not shown by FIG. 3). AMF 321 may act asSEAF, which may include interaction with the AUSF 322 and the UE 301,receipt of an intermediate key that was established as a result of theUE 301 authentication process. Where USIM based authentication is used,the AMF 321 may retrieve the security material from the AUSF 322. AMF321 may also include a SCM function, which receives a key from the SEAthat it uses to derive access-network specific keys. Furthermore, AMF321 may be a termination point of a RAN CP interface, which may includeor be an N2 reference point between the (R)AN 310 and the AMF 321; andthe AMF 321 may be a termination point of NAS (N1) signalling, andperform NAS ciphering and integrity protection.

AMF 321 may also support NAS signalling with a UE 301 over an N3 IWFinterface. The N3IWF may be used to provide access to untrustedentities. N3IWF may be a termination point for the N2 interface betweenthe (R)AN 310 and the AMF 321 for the control plane, and may be atermination point for the N3 reference point between the (R)AN 310 andthe UPF 302 for the user plane. As such, the AMF 321 may handle N2signalling from the SMF 324 and the AMF 321 for PDU sessions and QoS,encapsulate/de-encapsulate packets for IPSec and N3 tunnelling, mark N3user-plane packets in the uplink, and enforce QoS corresponding to N3packet marking taking into account QoS requirements associated with suchmarking received over N2. N3IWF may also relay uplink and downlinkcontrol-plane NAS signalling between the UE 301 and AMF 321 via an N1reference point between the UE 301 and the AMF 321, and relay uplink anddownlink user-plane packets between the UE 301 and UPF 302. The N3IWFalso provides mechanisms for IPsec tunnel establishment with the UE 301.The AMF 321 may exhibit an Namf service-based interface, and may be atermination point for an N14 reference point between two AMFs 321 and anN17 reference point between the AMF 321 and a 5G-EIR (not shown by FIG.3).

The UE 301 may need to register with the AMF 321 in order to receivenetwork services. RM is used to register or deregister the UE 301 withthe network (e.g., AMF 321), and establish a UE context in the network(e.g., AMF 321). The UE 301 may operate in an RM-REGISTERED state or anRM-DEREGISTERED state. In the RM-DEREGISTERED state, the UE 301 is notregistered with the network, and the UE context in AMF 321 holds novalid location or routing information for the UE 301 so the UE 301 isnot reachable by the AMF 321. In the RM-REGISTERED state, the UE 301 isregistered with the network, and the UE context in AMF 321 may hold avalid location or routing information for the UE 301 so the UE 301 isreachable by the AMF 321. In the RM-REGISTERED state, the UE 301 mayperform mobility Registration Update procedures, perform periodicRegistration Update procedures triggered by expiration of the periodicupdate timer (e.g., to notify the network that the UE 301 is stillactive), and perform a Registration Update procedure to update UEcapability information or to re-negotiate protocol parameters with thenetwork, among others.

The AMF 321 may store one or more RM contexts for the UE 301, where eachRM context is associated with a specific access to the network. The RMcontext may be a data structure, database object, etc. that indicates orstores, inter alia, a registration state per access type and theperiodic update timer. The AMF 321 may also store a 5GC MM context thatmay be the same or similar to the (E)MM context discussed previously. Invarious embodiments, the AMF 321 may store a CE mode B Restrictionparameter of the UE 301 in an associated MM context or RM context. TheAMF 321 may also derive the value, when needed, from the UE's usagesetting parameter already stored in the UE context (and/or MM/RMcontext).

CM may be used to establish and release a signaling connection betweenthe UE 301 and the AMF 321 over the N1 interface. The signalingconnection is used to enable NAS signaling exchange between the UE 301and the CN 320, and comprises both the signaling connection between theUE and the AN (e.g., RRC connection or UE-N3IWF connection for non-3GPPaccess) and the N2 connection for the UE 301 between the AN (e.g., RAN310) and the AMF 321. The UE 301 may operate in one of two CM states,CM-IDLE mode or CM-CONNECTED mode. When the UE 301 is operating in theCM-IDLE state/mode, the UE 301 may have no NAS signaling connectionestablished with the AMF 321 over the N1 interface, and there may be(R)AN 310 signaling connection (e.g., N2 and/or N3 connections) for theUE 301. When the UE 301 is operating in the CM-CONNECTED state/mode, theUE 301 may have an established NAS signaling connection with the AMF 321over the N1 interface, and there may be a (R)AN 310 signaling connection(e.g., N2 and/or N3 connections) for the UE 301. Establishment of an N2connection between the (R)AN 310 and the AMF 321 may cause the UE 301 totransition from CM-IDLE mode to CM-CONNECTED mode, and the UE 301 maytransition from the CM-CONNECTED mode to the CM-IDLE mode when N2signaling between the (R)AN 310 and the AMF 321 is released.

The SMF 324 may be responsible for SM (e.g., session establishment,modify and release, including tunnel maintain between UPF and AN node);UE IP address allocation and management (including optionalauthorization); selection and control of UP function; configuringtraffic steering at UPF to route traffic to proper destination;termination of interfaces toward policy control functions; controllingpart of policy enforcement and QoS; lawful intercept (for SM events andinterface to LI system); termination of SM parts of NAS messages;downlink data notification; initiating AN specific SM information, sentvia AMF over N2 to AN; and determining SSC mode of a session. SM refersto management of a PDU session, and a PDU session or “session” refers toa PDU connectivity service that provides or enables the exchange of PDUsbetween a UE 301 and a data network (DN) 303 identified by a DataNetwork Name (DNN). PDU sessions may be established upon UE 301 request,modified upon UE 301 and 5GC 320 request, and released upon UE 301 and5GC 320 request using NAS SM signaling exchanged over the N1 referencepoint between the UE 301 and the SMF 324. Upon request from anapplication server, the 5GC 320 may trigger a specific application inthe UE 301. In response to receipt of the trigger message, the UE 301may pass the trigger message (or relevant parts/information of thetrigger message) to one or more identified applications in the UE 301.The identified application(s) in the UE 301 may establish a PDU sessionto a specific DNN. The SMF 324 may check whether the UE 301 requests arecompliant with user subscription information associated with the UE 301.In this regard, the SMF 324 may retrieve and/or request to receiveupdate notifications on SMF 324 level subscription data from the UDM327.

The SMF 324 may include the following roaming functionality: handlinglocal enforcement to apply QoS SLAB (VPLMN); charging data collectionand charging interface (VPLMN); lawful intercept (in VPLMN for SM eventsand interface to LI system); and support for interaction with externalDN for transport of signalling for PDU sessionauthorization/authentication by external DN. An N16 reference pointbetween two SMFs 324 may be included in the system 300, which may bebetween another SMF 324 in a visited network and the SMF 324 in the homenetwork in roaming scenarios. Additionally, the SMF 324 may exhibit theNsmf service-based interface.

The NEF 323 may provide means for securely exposing the services andcapabilities provided by 3GPP network functions for third party,internal exposure/re-exposure, Application Functions (e.g., AF 328),edge computing or fog computing systems, etc. In such embodiments, theNEF 323 may authenticate, authorize, and/or throttle the AFs. NEF 323may also translate information exchanged with the AF 328 and informationexchanged with internal network functions. For example, the NEF 323 maytranslate between an AF-Service-Identifier and an internal 5GCinformation. NEF 323 may also receive information from other networkfunctions (NFs) based on exposed capabilities of other networkfunctions. This information may be stored at the NEF 323 as structureddata, or at a data storage NF using standardized interfaces. The storedinformation can then be re-exposed by the NEF 323 to other NFs and AFs,and/or used for other purposes such as analytics. Additionally, the NEF323 may exhibit an Nnef service-based interface.

The NRF 325 may support service discovery functions, receive NFdiscovery requests from NF instances, and provide the information of thediscovered NF instances to the NF instances. NRF 325 also maintainsinformation of available NF instances and their supported services. Asused herein, the terms “instantiate,” “instantiation,” and the likerefers to the creation of an instance, and an “instance” refers to aconcrete occurrence of an object, which may occur, for example, duringexecution of program code. Additionally, the NRF 325 may exhibit theNnrf service-based interface.

The PCF 326 may provide policy rules to control plane function(s) toenforce them, and may also support unified policy framework to governnetwork behaviour. The PCF 326 may also implement an FE to accesssubscription information relevant for policy decisions in a UDR of theUDM 327. The PCF 326 may communicate with the AMF 321 via an N15reference point between the PCF 326 and the AMF 321, which may include aPCF 326 in a visited network and the AMF 321 in case of roamingscenarios. The PCF 326 may communicate with the AF 328 via an N5reference point between the PCF 326 and the AF 328; and with the SMF 324via an N7 reference point between the PCF 326 and the SMF 324. Thesystem 300 and/or CN 320 may also include an N24 reference point betweenthe PCF 326 (in the home network) and a PCF 326 in a visited network.Additionally, the PCF 326 may exhibit an Npcf service-based interface.

The UDM 327 may handle subscription-related information to support thenetwork entities' handling of communication sessions, and may storesubscription data of UE 301. For example, subscription data may becommunicated between the UDM 327 and the AMF 321 via an N8 referencepoint between the UDM 327 and the AMF. The UDM 327 may include twoparts, an application FE and a UDR (the FE and UDR are not shown by FIG.3). The UDR may store subscription data and policy data for the UDM 327and the PCF 326, and/or structured data for exposure and applicationdata (including PFDs for application detection, application requestinformation for multiple UEs 301) for the NEF 323. The Nudrservice-based interface may be exhibited by the UDR 221 to allow the UDM327, PCF 326, and NEF 323 to access a particular set of the stored data,as well as to read, update (e.g., add, modify), delete, and subscribe tonotification of relevant data changes in the UDR. The UDM may include aUDM-FE, which is in charge of processing credentials, locationmanagement, subscription management and so on. Several different frontends may serve the same user in different transactions. The UDM-FEaccesses subscription information stored in the UDR and performsauthentication credential processing, user identification handling,access authorization, registration/mobility management, and subscriptionmanagement. The UDR may interact with the SMF 324 via an N10 referencepoint between the UDM 327 and the SMF 324. UDM 327 may also support SMSmanagement, wherein an SMS-FE implements the similar application logicas discussed previously. Additionally, the UDM 327 may exhibit the Nudmservice-based interface.

The AF 328 may provide application influence on traffic routing, provideaccess to the NCE, and interact with the policy framework for policycontrol. The NCE may be a mechanism that allows the 5GC 320 and AF 328to provide information to each other via NEF 323, which may be used foredge computing implementations. In such implementations, the networkoperator and third party services may be hosted close to the UE 301access point of attachment to achieve an efficient service deliverythrough the reduced end-to-end latency and load on the transportnetwork. For edge computing implementations, the 5GC may select a UPF302 close to the UE 301 and execute traffic steering from the UPF 302 toDN 303 via the N6 interface. This may be based on the UE subscriptiondata, UE location, and information provided by the AF 328. In this way,the AF 328 may influence UPF (re)selection and traffic routing. Based onoperator deployment, when AF 328 is considered to be a trusted entity,the network operator may permit AF 328 to interact directly withrelevant NFs. Additionally, the AF 328 may exhibit an Naf service-basedinterface.

The NSSF 329 may select a set of network slice instances serving the UE301. The NSSF 329 may also determine allowed NSSAI and the mapping tothe subscribed S-NSSAIs, if needed. The NSSF 329 may also determine theAMF set to be used to serve the UE 301, or a list of candidate AMF(s)321 based on a suitable configuration and possibly by querying the NRF325. The selection of a set of network slice instances for the UE 301may be triggered by the AMF 321 with which the UE 301 is registered byinteracting with the NSSF 329, which may lead to a change of AMF 321.The NSSF 329 may interact with the AMF 321 via an N22 reference pointbetween AMF 321 and NSSF 329; and may communicate with another NSSF 329in a visited network via an N31 reference point (not shown by FIG. 3).Additionally, the NSSF 329 may exhibit an Nnssf service-based interface.

As discussed previously, the CN 320 may include an SMSF, which may beresponsible for SMS subscription checking and verification, and relayingSM messages to/from the UE 301 to/from other entities, such as anSMS-GMSC/IWMSC/SMS-router. The SMS may also interact with AMF 321 andUDM 327 for a notification procedure that the UE 301 is available forSMS transfer (e.g., set a UE not reachable flag, and notifying UDM 327when UE 301 is available for SMS).

The CN 120 may also include other elements that are not shown by FIG. 3,such as a Data Storage system/architecture, a 5G-EIR, a SEPP, and thelike. The Data Storage system may include a SDSF, an UDSF, and/or thelike. Any NF may store and retrieve unstructured data into/from the UDSF(e.g., UE contexts), via N18 reference point between any NF and the UDSF(not shown by FIG. 3). Individual NFs may share a UDSF for storing theirrespective unstructured data or individual NFs may each have their ownUDSF located at or near the individual NFs. Additionally, the UDSF mayexhibit an Nudsf service-based interface (not shown by FIG. 3). The5G-EIR may be an NF that checks the status of PEI for determiningwhether particular equipment/entities are blacklisted from the network;and the SEPP may be a non-transparent proxy that performs topologyhiding, message filtering, and policing on inter-PLMN control planeinterfaces.

Additionally, there may be many more reference points and/orservice-based interfaces between the NF services in the NFs; however,these interfaces and reference points have been omitted from FIG. 3 forclarity. In one example, the CN 320 may include an Nx interface, whichis an inter-CN interface between the MME (e.g., MME 221) and the AMF 321in order to enable interworking between CN 320 and CN 220. Other exampleinterfaces/reference points may include an N5g-EIR service-basedinterface exhibited by a 5G-EIR, an N27 reference point between the NRFin the visited network and the NRF in the home network; and an N31reference point between the NSSF in the visited network and the NSSF inthe home network.

FIG. 4 illustrates an example of infrastructure equipment 400 inaccordance with various embodiments. The infrastructure equipment 400(or “system 400”) may be implemented as a base station, radio head, RANnode such as the RAN nodes 111 and/or AP 106 shown and describedpreviously, application server(s) 130, and/or any other element/devicediscussed herein. In other examples, the system 400 could be implementedin or by a UE.

The system 400 includes application circuitry 405, baseband circuitry410, one or more radio front end modules (RFEMs) 415, memory circuitry420, power management integrated circuitry (PMIC) 425, power teecircuitry 430, network controller circuitry 435, network interfaceconnector 440, satellite positioning circuitry 445, and user interface450. In some embodiments, the device 400 may include additional elementssuch as, for example, memory/storage, display, camera, sensor, orinput/output (I/O) interface. In other embodiments, the componentsdescribed below may be included in more than one device. For example,said circuitries may be separately included in more than one device forCRAN, vBBU, or other like implementations.

Application circuitry 405 includes circuitry such as, but not limited toone or more processors (or processor cores), cache memory, and one ormore of low drop-out voltage regulators (LDOs), interrupt controllers,serial interfaces such as SPI, I²C or universal programmable serialinterface module, real time clock (RTC), timer-counters includinginterval and watchdog timers, general purpose input/output (I/O or IO),memory card controllers such as Secure Digital (SD) MultiMediaCard (MMC)or similar, Universal Serial Bus (USB) interfaces, Mobile IndustryProcessor Interface (MIPI) interfaces and Joint Test Access Group (JTAG)test access ports. The processors (or cores) of the applicationcircuitry 405 may be coupled with or may include memory/storage elementsand may be configured to execute instructions stored in thememory/storage to enable various applications or operating systems torun on the system 400. In some implementations, the memory/storageelements may be on-chip memory circuitry, which may include any suitablevolatile and/or non-volatile memory, such as DRAM, SRAM, EPROM, EEPROM,Flash memory, solid-state memory, and/or any other type of memory devicetechnology, such as those discussed herein.

The processor(s) of application circuitry 405 may include, for example,one or more processor cores (CPUs), one or more application processors,one or more graphics processing units (GPUs), one or more reducedinstruction set computing (RISC) processors, one or more Acorn RISCMachine (ARM) processors, one or more complex instruction set computing(CISC) processors, one or more digital signal processors (DSP), one ormore FPGAs, one or more PLDs, one or more ASICs, one or moremicroprocessors or controllers, or any suitable combination thereof. Insome embodiments, the application circuitry 405 may comprise, or may be,a special-purpose processor/controller to operate according to thevarious embodiments herein. As examples, the processor(s) of applicationcircuitry 405 may include one or more Intel Pentium®, Core®, or Xeon®processor(s); Advanced Micro Devices (AMD) Ryzen® processor(s),Accelerated Processing Units (APUs), or Epyc® processors; ARM-basedprocessor(s) licensed from ARM Holdings, Ltd. such as the ARM Cortex-Afamily of processors and the ThunderX2® provided by Cavium™, Inc.; aMIPS-based design from MIPS Technologies, Inc. such as MIPS WarriorP-class processors; and/or the like. In some embodiments, the system 400may not utilize application circuitry 405, and instead may include aspecial-purpose processor/controller to process IP data received from anEPC or 5GC, for example.

In some implementations, the application circuitry 405 may include oneor more hardware accelerators, which may be microprocessors,programmable processing devices, or the like. The one or more hardwareaccelerators may include, for example, computer vision (CV) and/or deeplearning (DL) accelerators. As examples, the programmable processingdevices may be one or more a field-programmable devices (FPDs) such asfield-programmable gate arrays (FPGAs) and the like; programmable logicdevices (PLDs) such as complex PLDs (CPLDs), high-capacity PLDs(HCPLDs), and the like; ASICs such as structured ASICs and the like;programmable SoCs (PSoCs); and the like. In such implementations, thecircuitry of application circuitry 405 may comprise logic blocks orlogic fabric, and other interconnected resources that may be programmedto perform various functions, such as the procedures, methods,functions, etc. of the various embodiments discussed herein. In suchembodiments, the circuitry of application circuitry 405 may includememory cells (e.g., erasable programmable read-only memory (EPROM),electrically erasable programmable read-only memory (EEPROM), flashmemory, static memory (e.g., static random access memory (SRAM),anti-fuses, etc.)) used to store logic blocks, logic fabric, data, etc.in look-up-tables (LUTs) and the like.

The baseband circuitry 410 may be implemented, for example, as asolder-down substrate including one or more integrated circuits, asingle packaged integrated circuit soldered to a main circuit board or amulti-chip module containing two or more integrated circuits. Thevarious hardware electronic elements of baseband circuitry 410 arediscussed infra with regard to FIG. 7.

User interface circuitry 450 may include one or more user interfacesdesigned to enable user interaction with the system 400 or peripheralcomponent interfaces designed to enable peripheral component interactionwith the system 400. User interfaces may include, but are not limitedto, one or more physical or virtual buttons (e.g., a reset button), oneor more indicators (e.g., light emitting diodes (LEDs)), a physicalkeyboard or keypad, a mouse, a touchpad, a touchscreen, speakers orother audio emitting devices, microphones, a printer, a scanner, aheadset, a display screen or display device, etc. Peripheral componentinterfaces may include, but are not limited to, a nonvolatile memoryport, a universal serial bus (USB) port, an audio jack, a power supplyinterface, etc.

The radio front end modules (RFEMs) 415 may comprise a millimeter wave(mmWave) RFEM and one or more sub-mmWave radio frequency integratedcircuits (RFICs). In some implementations, the one or more sub-mmWaveRFICs may be physically separated from the mmWave RFEM. The RFICs mayinclude connections to one or more antennas or antenna arrays (see e.g.,antenna array 711 of FIG. 7 infra), and the RFEM may be connected tomultiple antennas. In alternative implementations, both mmWave andsub-mmWave radio functions may be implemented in the same physical RFEM415, which incorporates both mmWave antennas and sub-mmWave.

The memory circuitry 420 may include one or more of volatile memoryincluding dynamic random access memory (DRAM) and/or synchronous dynamicrandom access memory (SDRAM), and nonvolatile memory (NVM) includinghigh-speed electrically erasable memory (commonly referred to as Flashmemory), phase change random access memory (PRAM), magnetoresistiverandom access memory (MRAM), etc., and may incorporate thethree-dimensional (3D) cross-point (XPOINT) memories from Intel® andMicron®. Memory circuitry 420 may be implemented as one or more ofsolder down packaged integrated circuits, socketed memory modules andplug-in memory cards.

The PMIC 425 may include voltage regulators, surge protectors, poweralarm detection circuitry, and one or more backup power sources such asa battery or capacitor. The power alarm detection circuitry may detectone or more of brown out (under-voltage) and surge (over-voltage)conditions. The power tee circuitry 430 may provide for electrical powerdrawn from a network cable to provide both power supply and dataconnectivity to the infrastructure equipment 400 using a single cable.

The network controller circuitry 435 may provide connectivity to anetwork using a standard network interface protocol such as Ethernet,Ethernet over GRE Tunnels, Ethernet over Multiprotocol Label Switching(MPLS), or some other suitable protocol. Network connectivity may beprovided to/from the infrastructure equipment 400 via network interfaceconnector 440 using a physical connection, which may be electrical(commonly referred to as a “copper interconnect”), optical, or wireless.The network controller circuitry 435 may include one or more dedicatedprocessors and/or FPGAs to communicate using one or more of theaforementioned protocols. In some implementations, the networkcontroller circuitry 435 may include multiple controllers to provideconnectivity to other networks using the same or different protocols.

The positioning circuitry 445 includes circuitry to receive and decodesignals transmitted/broadcasted by a positioning network of a globalnavigation satellite system (GNSS). Examples of navigation satelliteconstellations (or GNSS) include United States' Global PositioningSystem (GPS), Russia's Global Navigation System (GLONASS), the EuropeanUnion's Galileo system, China's BeiDou Navigation Satellite System, aregional navigation system or GNSS augmentation system (e.g., Navigationwith Indian Constellation (NAVIC), Japan's Quasi-Zenith Satellite System(QZSS), France's Doppler Orbitography and Radio-positioning Integratedby Satellite (DORIS), etc.), or the like. The positioning circuitry 445comprises various hardware elements (e.g., including hardware devicessuch as switches, filters, amplifiers, antenna elements, and the like tofacilitate OTA communications) to communicate with components of apositioning network, such as navigation satellite constellation nodes.In some embodiments, the positioning circuitry 445 may include aMicro-Technology for Positioning, Navigation, and Timing (Micro-PNT) ICthat uses a master timing clock to perform position tracking/estimationwithout GNSS assistance. The positioning circuitry 445 may also be partof, or interact with, the baseband circuitry 410 and/or RFEMs 415 tocommunicate with the nodes and components of the positioning network.The positioning circuitry 445 may also provide position data and/or timedata to the application circuitry 405, which may use the data tosynchronize operations with various infrastructure (e.g., RAN nodes 111,etc.), or the like.

The components shown by FIG. 4 communicate with one another usinginterface circuitry, which may include interconnect (IX) 406. The IX 406may include any number of bus and/or IX technologies such as industrystandard architecture (ISA), extended ISA (EISA), inter-integratedcircuit (I²C), an serial peripheral interface (SPI), point-to-pointinterfaces, power management bus (PMBus), peripheral componentinterconnect (PCI), PCI express (PCIe), Intel® Ultra Path Interface(UPI), Intel® Accelerator Link (IAL), Common Application ProgrammingInterface (CAPI), Intel® QuickPath interconnect (QPI), Ultra PathInterconnect (UPI), Intel® Omni-Path Architecture (OPA) IX, RapidIO™system IXs, Cache Coherent Interconnect for Accelerators (CCIA), Gen-ZConsortium IXs, Open Coherent Accelerator Processor Interface (OpenCAPI)IX, a HyperTransport interconnect, and/or any number of other IXtechnologies. The IX technology may be a proprietary bus, for example,used in an SoC based system.

FIG. 5 illustrates an example of a platform 500 (or “device 500”) inaccordance with various embodiments. In embodiments, the computerplatform 500 may be suitable for use as UEs 101, 202, 301, applicationservers 130, and/or any other element/device discussed herein. Theplatform 500 may include any combinations of the components shown in theexample. The components of platform 500 may be implemented as integratedcircuits (ICs), portions thereof, discrete electronic devices, or othermodules, logic, hardware, software, firmware, or a combination thereofadapted in the computer platform 500, or as components otherwiseincorporated within a chassis of a larger system. The block diagram ofFIG. 5 is intended to show a high level view of components of thecomputer platform 500. However, some of the components shown may beomitted, additional components may be present, and different arrangementof the components shown may occur in other implementations.

Application circuitry 505 includes circuitry such as, but not limited toone or more processors (or processor cores), cache memory, and one ormore of LDOs, interrupt controllers, serial interfaces such as SPI, I²Cor universal programmable serial interface module, RTC, timer-countersincluding interval and watchdog timers, general purpose I/O, memory cardcontrollers such as SD MMC or similar, USB interfaces, MIPI interfaces,and JTAG test access ports. The processors (or cores) of the applicationcircuitry 505 may be coupled with or may include memory/storage elementsand may be configured to execute instructions stored in thememory/storage to enable various applications or operating systems torun on the system 500. In some implementations, the memory/storageelements may be on-chip memory circuitry, which may include any suitablevolatile and/or non-volatile memory, such as DRAM, SRAM, EPROM, EEPROM,Flash memory, solid-state memory, and/or any other type of memory devicetechnology, such as those discussed herein.

The processor(s) of application circuitry 405 may include, for example,one or more processor cores, one or more application processors, one ormore GPUs, one or more RISC processors, one or more ARM processors, oneor more CISC processors, one or more DSP, one or more FPGAs, one or morePLDs, one or more ASICs, one or more microprocessors or controllers, amultithreaded processor, an ultra-low voltage processor, an embeddedprocessor, some other known processing element, or any suitablecombination thereof. The processors (or cores) of the applicationcircuitry 405 may be coupled with or may include memory/storage and maybe configured to execute instructions stored in the memory/storage toenable various applications or operating systems to run on the system500. In these embodiments, the processors (or cores) of the applicationcircuitry 405 are configured to operate application software to providea specific service to a user of the system 500. In some embodiments, theapplication circuitry 405 may comprise, or may be, a special-purposeprocessor/controller to operate according to the various embodimentsherein.

As examples, the processor(s) of application circuitry 505 may includean Intel® Architecture Core™ based processor, such as a Quark™, anAtom™, an i3, an i5, an i7, or an MCU-class processor, or another suchprocessor available from Intel® Corporation, Santa Clara, Calif. Theprocessors of the application circuitry 505 may also be one or more ofAdvanced Micro Devices (AMD) Ryzen® processor(s) or AcceleratedProcessing Units (APUs); A5-A9 processor(s) from Apple® Inc.,Snapdragon™ processor(s) from Qualcomm® Technologies, Inc., TexasInstruments, Inc.® Open Multimedia Applications Platform (OMAP)™processor(s); a MIPS-based design from MIPS Technologies, Inc. such asMIPS Warrior M-class, Warrior I-class, and Warrior P-class processors;an ARM-based design licensed from ARM Holdings, Ltd., such as the ARMCortex-A, Cortex-R, and Cortex-M family of processors; or the like. Insome implementations, the application circuitry 505 may be a part of asystem on a chip (SoC) in which the application circuitry 505 and othercomponents are formed into a single integrated circuit, or a singlepackage, such as the Edison™ or Galileo™ SoC boards from Intel®Corporation. Other examples of the processor circuitry of applicationcircuitry 405 are mentioned elsewhere in the present disclosure.

Additionally or alternatively, application circuitry 505 may includecircuitry such as, but not limited to, one or more a field-programmabledevices (FPDs) such as FPGAs and the like; programmable logic devices(PLDs) such as complex PLDs (CPLDs), high-capacity PLDs (HCPLDs), andthe like; ASICs such as structured ASICs and the like; programmable SoCs(PSoCs); and the like. In such embodiments, the circuitry of applicationcircuitry 505 may comprise logic blocks or logic fabric, and otherinterconnected resources that may be programmed to perform variousfunctions, such as the procedures, methods, functions, etc. of thevarious embodiments discussed herein. In such embodiments, the circuitryof application circuitry 505 may include memory cells (e.g., erasableprogrammable read-only memory (EPROM), electrically erasableprogrammable read-only memory (EEPROM), flash memory, static memory(e.g., static random access memory (SRAM), anti-fuses, etc.)) used tostore logic blocks, logic fabric, data, etc. in look-up tables (LUTs)and the like.

The baseband circuitry 510 may be implemented, for example, as asolder-down substrate including one or more integrated circuits, asingle packaged integrated circuit soldered to a main circuit board or amulti-chip module containing two or more integrated circuits. Thebaseband circuitry 510 may include circuitry such as, but not limitedto, one or more single-core or multi-core processors (e.g., one or morebaseband processors) or control logic to process baseband signalsreceived from a receive signal path of the RFEMs 515, and to generatebaseband signals to be provided to the RFEMs 515 via a transmit signalpath. In various embodiments, the baseband circuitry 510 may implement areal-time OS (RTOS) to manage resources of the baseband circuitry 510,schedule tasks, etc. Examples of the RTOS may include Operating SystemEmbedded (OSE)™ provided by Enea®, Nucleus RTOS™ provided by MentorGraphics®, Versatile Real-Time Executive (VRTX) provided by MentorGraphics®, ThreadX™ provided by Express Logic®, FreeRTOS, REX OSprovided by Qualcomm®, OKL4 provided by Open Kernel (OK) Labs®, or anyother suitable RTOS, such as those discussed herein. The varioushardware electronic elements of baseband circuitry 510 are discussedinfra with regard to FIG. 7.

The RFEMs 515 may comprise a millimeter wave (mmWave) RFEM and one ormore sub-mmWave radio frequency integrated circuits (RFICs). In someimplementations, the one or more sub-mmWave RFICs may be physicallyseparated from the mmWave RFEM. The RFICs may include connections to oneor more antennas or antenna arrays (see e.g., antenna array 711 of FIG.7 infra), and the RFEM may be connected to multiple antennas. Inalternative implementations, both mmWave and sub-mmWave radio functionsmay be implemented in the same physical RFEM 515, which incorporatesboth mmWave antennas and sub-mmWave.

The memory circuitry 520 may include any number and type of memorydevices used to provide for a given amount of system memory. Asexamples, the memory circuitry 520 may include one or more of volatilememory including random access memory (RAM), dynamic RAM (DRAM) and/orsynchronous dynamic RAM (SDRAM), and nonvolatile memory (NVM) includinghigh-speed electrically erasable memory (commonly referred to as Flashmemory), phase change random access memory (PRAM), magnetoresistiverandom access memory (MRAM), etc. The memory circuitry 520 may bedeveloped in accordance with a Joint Electron Devices EngineeringCouncil (JEDEC) low power double data rate (LPDDR)-based design, such asLPDDR2, LPDDR3, LPDDR4, or the like. Memory circuitry 520 may beimplemented as one or more of solder down packaged integrated circuits,single die package (SDP), dual die package (DDP) or quad die package(Q17P), socketed memory modules, dual inline memory modules (DIMMs)including microDIMMs or MiniDIMMs, and/or soldered onto a motherboardvia a ball grid array (BGA). In low power implementations, the memorycircuitry 520 may be on-die memory or registers associated with theapplication circuitry 505. To provide for persistent storage ofinformation such as data, applications, operating systems and so forth,memory circuitry 520 may include one or more mass storage devices, whichmay include, inter alia, a solid state disk drive (SSDD), hard diskdrive (HDD), a micro HDD, resistance change memories, phase changememories, holographic memories, or chemical memories, among others. Forexample, the computer platform 500 may incorporate the three-dimensional(3D) cross-point (XPOINT) memories from Intel® and Micron®.

Removable memory circuitry 523 may include devices, circuitry,enclosures/housings, ports or receptacles, etc. used to couple portabledata storage devices with the platform 500. These portable data storagedevices may be used for mass storage purposes, and may include, forexample, flash memory cards (e.g., Secure Digital (SD) cards, microSDcards, xD picture cards, and the like), and USB flash drives, opticaldiscs, external HDDs, and the like.

In some implementations, the memory circuitry 520 and/or the removablememory 523 provide persistent storage of information such as data,applications, operating systems (OS), and so forth. The persistentstorage circuitry is configured to store computational logic (or“modules”) in the form of software, firmware, or hardware commands toimplement the techniques described herein. The computational logic maybe employed to store working copies and/or permanent copies of computerprograms (or data to create the computer programs) for the operation ofvarious components of platform 500 (e.g., drivers, etc.), an operatingsystem of platform 500, one or more applications, and/or for carryingout the embodiments discussed herein. The computational logic may bestored or loaded into memory circuitry 520 as instructions (or data tocreate the instructions) for execution by the application circuitry 505to provide the functions described herein. The various elements may beimplemented by assembler instructions supported by processor circuitryor high-level languages that may be compiled into such instructions (ordata to create the instructions). The permanent copy of the programminginstructions may be placed into persistent storage devices of persistentstorage circuitry in the factory or in the field through, for example, adistribution medium (not shown), through a communication interface(e.g., from a distribution server (not shown)), or OTA.

In an example, the instructions provided via the memory circuitry 520and/or the persistent storage circuitry are embodied as one or morenon-transitory computer readable storage media including program code, acomputer program product (or data to create the computer program) withthe computer program or data, to direct the application circuitry 505 ofplatform 500 to perform electronic operations in the platform 500,and/or to perform a specific sequence or flow of actions, for example,as described with respect to the flowchart(s) and block diagram(s) ofoperations and functionality depicted infra (see e.g., FIGS. 9-11). Theapplication circuitry 505 accesses the one or more non-transitorycomputer readable storage media over the IX 506.

Although the instructions and/or computational logic have been describedas code blocks included in the memory circuitry 520 and/or code blocksin the persistent storage circuitry, it should be understood that any ofthe code blocks may be replaced with hardwired circuits, for example,built into an FPGA, ASIC, or some other suitable circuitry. For example,where application circuitry 505 includes (e.g., FPGA based) hardwareaccelerators as well as processor cores, the hardware accelerators(e.g., the FPGA cells) may be pre-configured (e.g., with appropriate bitstreams) with the aforementioned computational logic to perform some orall of the functions discussed previously (in lieu of employment ofprogramming instructions to be executed by the processor core(s)).

The platform 500 may also include interface circuitry (not shown) thatis used to connect external devices with the platform 500. The externaldevices connected to the platform 500 via the interface circuitryinclude sensor circuitry 521 and actuators 522, as well as removablememory devices coupled to removable memory circuitry 523.

The sensor circuitry 521 include devices, modules, or subsystems whosepurpose is to detect events or changes in its environment and send theinformation (sensor data) about the detected events to some other adevice, module, subsystem, etc. Examples of such sensors include, interalia, inertia measurement units (IMUS) comprising accelerometers,gyroscopes, and/or magnetometers; microelectromechanical systems (MEMS)or nanoelectromechanical systems (NEMS) comprising 3-axisaccelerometers, 3-axis gyroscopes, and/or magnetometers; level sensors;flow sensors; temperature sensors (e.g., thermistors); pressure sensors;barometric pressure sensors; gravimeters; altimeters; image capturedevices (e.g., cameras or lensless apertures); light detection andranging (LiDAR) sensors; proximity sensors (e.g., infrared radiationdetector and the like), depth sensors, ambient light sensors, ultrasonictransceivers; microphones or other like audio capture devices; etc.

Actuators 522 include devices, modules, or subsystems whose purpose isto enable platform 500 to change its state, position, and/ororientation, or move or control a mechanism or (sub)system. Theactuators 522 comprise electrical and/or mechanical devices for movingor controlling a mechanism or system, and converts energy (e.g.,electric current or moving air and/or liquid) into some kind of motion.The actuators 522 may include one or more electronic (orelectrochemical) devices, such as piezoelectric biomorphs, solid stateactuators, solid state relays (SSRs), shape-memory alloy-basedactuators, electroactive polymer-based actuators, relay driverintegrated circuits (ICs), and/or the like. The actuators 522 mayinclude one or more electromechanical devices such as pneumaticactuators, hydraulic actuators, electromechanical switches includingelectromechanical relays (EMRs), motors (e.g., DC motors, steppermotors, servomechanisms, etc.), wheels, thrusters, propellers, claws,clamps, hooks, an audible sound generator, and/or other likeelectromechanical components. The platform 1000 may be configured tooperate one or more actuators 522 based on one or more captured eventsand/or instructions or control signals received from a service providerand/or various client systems.

In some implementations, the interface circuitry may connect theplatform 500 with positioning circuitry 545. The positioning circuitry545 includes circuitry to receive and decode signalstransmitted/broadcasted by a positioning network of a GNSS. Examples ofnavigation satellite constellations (or GNSS) include United States'GPS, Russia's GLONASS, the European Union's Galileo system, China'sBeiDou Navigation Satellite System, a regional navigation system or GNSSaugmentation system (e.g., NAVIC), Japan's QZSS, France's DORIS, etc.),or the like. The positioning circuitry 545 comprises various hardwareelements (e.g., including hardware devices such as switches, filters,amplifiers, antenna elements, and the like to facilitate OTAcommunications) to communicate with components of a positioning network,such as navigation satellite constellation nodes. In some embodiments,the positioning circuitry 545 may include a Micro-PNT IC that uses amaster timing clock to perform position tracking/estimation without GNSSassistance. The positioning circuitry 545 may also be part of, orinteract with, the baseband circuitry 510 and/or RFEMs 515 tocommunicate with the nodes and components of the positioning network.The positioning circuitry 545 may also provide position data and/or timedata to the application circuitry 505, which may use the data tosynchronize operations with various infrastructure (e.g., radio basestations), for turn-by-turn navigation applications, or the like

In some implementations, the interface circuitry may connect theplatform 500 with Near-Field Communication (NFC) circuitry 540. NFCcircuitry 540 is configured to provide contactless, short-rangecommunications based on radio frequency identification (RFID) standards,wherein magnetic field induction is used to enable communication betweenNFC circuitry 540 and NFC-enabled devices external to the platform 500(e.g., an “NFC touchpoint”). NFC circuitry 540 comprises an NFCcontroller coupled with an antenna element and a processor coupled withthe NFC controller. The NFC controller may be a chip/IC providing NFCfunctionalities to the NFC circuitry 540 by executing NFC controllerfirmware and an NFC stack. The NFC stack may be executed by theprocessor to control the NFC controller, and the NFC controller firmwaremay be executed by the NFC controller to control the antenna element toemit short-range RF signals. The RF signals may power a passive NFC tag(e.g., a microchip embedded in a sticker or wristband) to transmitstored data to the NFC circuitry 540, or initiate data transfer betweenthe NFC circuitry 540 and another active NFC device (e.g., a smartphoneor an NFC-enabled POS terminal) that is proximate to the platform 500.

The driver circuitry 546 may include software and hardware elements thatoperate to control particular devices that are embedded in the platform500, attached to the platform 500, or otherwise communicatively coupledwith the platform 500. The driver circuitry 546 may include individualdrivers allowing other components of the platform 500 to interact withor control various input/output (I/O) devices that may be presentwithin, or connected to, the platform 500. For example, driver circuitry546 may include a display driver to control and allow access to adisplay device, a touchscreen driver to control and allow access to atouchscreen interface of the platform 500, sensor drivers to obtainsensor readings of sensor circuitry 521 and control and allow access tosensor circuitry 521, actuator drivers to obtain actuator positions ofthe actuators 522 and/or control and allow access to the actuators 522,a camera driver to control and allow access to an embedded image capturedevice, audio drivers to control and allow access to one or more audiodevices.

The power management integrated circuitry (PMIC) 525 (also referred toas “power management circuitry 525”) may manage power provided tovarious components of the platform 500. In particular, with respect tothe baseband circuitry 510, the PMIC 525 may control power-sourceselection, voltage scaling, battery charging, or DC-to-DC conversion.The PMIC 525 may often be included when the platform 500 is capable ofbeing powered by a battery 530, for example, when the device is includedin a UE 101, 201, 301.

In some embodiments, the PMIC 525 may control, or otherwise be part of,various power saving mechanisms of the platform 500. For example, if theplatform 500 is in an RRC_Connected state, where it is still connectedto the RAN node as it expects to receive traffic shortly, then it mayenter a state known as DRX after a period of inactivity. During thisstate, the platform 500 may power down for brief intervals of time andthus save power. If there is no data traffic activity for an extendedperiod of time, then the platform 500 may transition off to an RRC Idlestate, where it disconnects from the network and does not performoperations such as channel quality feedback, handover, etc. The platform500 goes into a very low power state and it performs paging where againit periodically wakes up to listen to the network and then powers downagain. The platform 500 may not receive data in this state; in order toreceive data, it must transition back to RRC_Connected state. Anadditional power saving mode may allow a device to be unavailable to thenetwork for periods longer than a paging interval (ranging from secondsto a few hours). During this time, the device is totally unreachable tothe network and may power down completely. Any data sent during thistime incurs a large delay and it is assumed the delay is acceptable.

A battery 530 may power the platform 500, although in some examples theplatform 500 may be mounted deployed in a fixed location, and may have apower supply coupled to an electrical grid. The battery 530 may be alithium ion battery, a metal-air battery, such as a zinc-air battery, analuminum-air battery, a lithium-air battery, and the like. In someimplementations, such as in V2X applications, the battery 530 may be atypical lead-acid automotive battery.

In some implementations, the battery 530 may be a “smart battery,” whichincludes or is coupled with a Battery Management System (BMS) or batterymonitoring integrated circuitry. The BMS may be included in the platform500 to track the state of charge (SoCh) of the battery 530. The BMS maybe used to monitor other parameters of the battery 530 to providefailure predictions, such as the state of health (SoH) and the state offunction (SoF) of the battery 530. The BMS may communicate theinformation of the battery 530 to the application circuitry 505 or othercomponents of the platform 500. The BMS may also include ananalog-to-digital (ADC) convertor that allows the application circuitry505 to directly monitor the voltage of the battery 530 or the currentflow from the battery 530. The battery parameters may be used todetermine actions that the platform 500 may perform, such astransmission frequency, network operation, sensing frequency, and thelike.

A power block, or other power supply coupled to an electrical grid maybe coupled with the BMS to charge the battery 530. In some examples, thepower block XS30 may be replaced with a wireless power receiver toobtain the power wirelessly, for example, through a loop antenna in thecomputer platform 500. In these examples, a wireless battery chargingcircuit may be included in the BMS. The specific charging circuitschosen may depend on the size of the battery 530, and thus, the currentrequired. The charging may be performed using the Airfuel standardpromulgated by the Airfuel Alliance, the Qi wireless charging standardpromulgated by the Wireless Power Consortium, or the Rezence chargingstandard promulgated by the Alliance for Wireless Power, among others.

User interface circuitry 550 includes various input/output (I/O) devicespresent within, or connected to, the platform 500, and includes one ormore user interfaces designed to enable user interaction with theplatform 500 and/or peripheral component interfaces designed to enableperipheral component interaction with the platform 500. The userinterface circuitry 550 includes input device circuitry and outputdevice circuitry. Input device circuitry includes any physical orvirtual means for accepting an input including, inter alia, one or morephysical or virtual buttons (e.g., a reset button), a physical keyboard,keypad, mouse, touchpad, touchscreen, microphones, scanner, headset,and/or the like. The output device circuitry includes any physical orvirtual means for showing information or otherwise conveyinginformation, such as sensor readings, actuator position(s), or otherlike information. Output device circuitry may include any number and/orcombinations of audio or visual display, including, inter alia, one ormore simple visual outputs/indicators (e.g., binary status indicators(e.g., light emitting diodes (LEDs)) and multi-character visual outputs,or more complex outputs such as display devices or touchscreens (e.g.,Liquid Chrystal Displays (LCD), LED displays, quantum dot displays,projectors, etc.), with the output of characters, graphics, multimediaobjects, and the like being generated or produced from the operation ofthe platform 500. The output device circuitry may also include speakersor other audio emitting devices, printer(s), and/or the like. In someembodiments, the sensor circuitry 521 may be used as the input devicecircuitry (e.g., an image capture device, motion capture device, or thelike) and one or more actuators 522 may be used as the output devicecircuitry (e.g., an actuator to provide haptic feedback or the like). Inanother example, NFC circuitry comprising an NFC controller coupled withan antenna element and a processing device may be included to readelectronic tags and/or connect with another NFC-enabled device.Peripheral component interfaces may include, but are not limited to, anon-volatile memory port, a USB port, an audio jack, a power supplyinterface, etc.

The components shown by FIG. 5 communicate with one another usinginterface circuitry, which may include interconnect (IX) 506. The IX 506may include any number of bus and/or IX technologies such as ISA, EISA,I²C, SPI, point-to-point interfaces, PMBus, PCI) PCIe, Intel® UPI, IAL,CAPI, Intel® QPI, UPI, Intel® OPA IX, RapidIO™ system IXs, CCIA, Gen-ZConsortium IXs, OpenCAPI IX, a HyperTransport interconnect, Time-TriggerProtocol (TTP) system, a FlexRay system, and/or any number of other IXtechnologies. The IX technology may be a proprietary bus, for example,used in an SoC based system.

FIG. 6 illustrates components, according to some example embodiments,able to read instructions from a machine-readable or computer-readablemedium (e.g., a non-transitory machine-readable storage medium) andperform any one or more of the methodologies discussed herein.Specifically, FIG. 6 shows a diagrammatic representation of hardwareresources 600 including one or more processors (or processor cores) 610,one or more memory/storage devices 620, and one or more communicationresources 630, each of which may be communicatively coupled via a bus640. For embodiments where node virtualization (e.g., NFV) is utilized,a hypervisor 602 may be executed to provide an execution environment forone or more network slices/sub-slices to utilize the hardware resources600.

The processors 610 may include, for example, a processor 612 and aprocessor 614. The processor(s) 610 may be, for example, a CPU, areduced instruction set computing (RISC) processor, a CISC processor, aGPU, a DSP such as a baseband processor, an ASIC, an FPGA, a RFIC,another processor (including those discussed herein), or any suitablecombination thereof. The memory/storage devices 620 may include mainmemory, disk storage, or any suitable combination thereof. Thememory/storage devices 620 may include, but are not limited to, any typeof volatile or nonvolatile memory such as DRAM, SRAM, EPROM, EEPROM,Flash memory, solid-state storage, etc.

The communication resources 630 may include interconnection or networkinterface components or other suitable devices to communicate with oneor more peripheral devices 604 or one or more databases 606 via anetwork 608. For example, the communication resources 630 may includewired communication components (e.g., for coupling via USB), cellularcommunication components, NFC components, Bluetooth® (or Bluetooth® LowEnergy) components, Wi-Fi® components, and other communicationcomponents, such as those discussed herein.

Instructions 650 may comprise software, a program, an application, anapplet, an app, or other executable code for causing at least any of theprocessors 610 to perform any one or more of the methodologies discussedherein. The instructions 650 may reside, completely or partially, withinat least one of the processors 610 (e.g., within the processor's cachememory), the memory/storage devices 620, or any suitable combinationthereof. Furthermore, any portion of the instructions 650 may betransferred to the hardware resources 600 from any combination of theperipheral devices 604 or the databases 606. Accordingly, the memory ofprocessors 610, the memory/storage devices 620, the peripheral devices604, and the databases 606 are examples of computer-readable andmachine-readable media.

FIG. 7 illustrates example components of baseband circuitry 710 andradio front end modules (RFEM) 715 in accordance with variousembodiments. The baseband circuitry 710 corresponds to the basebandcircuitry 410 and 510 of FIGS. 4 and 5, respectively. The RFEM 715corresponds to the RFEM 415 and 515 of FIGS. 4 and 5, respectively. Asshown, the RFEMs 715 may include Radio Frequency (RF) circuitry 706,front-end module (FEM) circuitry 708, antenna array 711 coupled togetherat least as shown.

The baseband circuitry 710 includes circuitry and/or control logicconfigured to carry out various radio/network protocol and radio controlfunctions that enable communication with one or more radio networks viathe RF circuitry 706. The radio control functions may include, but arenot limited to, signal modulation/demodulation, encoding/decoding, radiofrequency shifting, etc. In some embodiments, modulation/demodulationcircuitry of the baseband circuitry 710 may include Fast-FourierTransform (FFT), precoding, or constellation mapping/demappingfunctionality. In some embodiments, encoding/decoding circuitry of thebaseband circuitry 710 may include convolution, tail-biting convolution,turbo, Viterbi, LDPC, and/or polar code encoder/decoder functionality.Embodiments of modulation/demodulation and encoder/decoder functionalityare not limited to these examples and may include other suitablefunctionality in other embodiments. The baseband circuitry 710 isconfigured to process baseband signals received from a receive signalpath of the RF circuitry 706 and to generate baseband signals for atransmit signal path of the RF circuitry 706. The baseband circuitry 710is configured to interface with application circuitry 405/505 (see FIGS.4 and 5) for generation and processing of the baseband signals and forcontrolling operations of the RF circuitry 706. The baseband circuitry710 may handle various radio control functions.

The aforementioned circuitry and/or control logic of the basebandcircuitry 710 may include one or more single or multi-core processors.For example, the one or more processors may include a 3G basebandprocessor 704A, a 4G/LTE baseband processor 704B, a 5G/NR basebandprocessor 704C, or some other baseband processor(s) 704D for otherexisting generations, generations in development or to be developed inthe future (e.g., 6G, etc.). In other embodiments, some or all of thefunctionality of baseband processors 704A-D may be included in modulesstored in the memory 704G and executed via a CPU 704E. In otherembodiments, some or all of the functionality of baseband processors704A-D may be provided as hardware accelerators (e.g., FPGAs, ASICs,etc.) loaded with the appropriate bit streams or logic blocks stored inrespective memory cells. In various embodiments, the memory 704G maystore program code of a real-time OS (RTOS), which when executed by theCPU 704E (or other baseband processor), is to cause the CPU 704E (orother baseband processor) to manage resources of the baseband circuitry710, schedule tasks, etc. Examples of the RTOS may include OperatingSystem Embedded (OSE)™ provided by Enea®, Nucleus RTOS™ provided byMentor Graphics®, Versatile Real-Time Executive (VRTX) provided byMentor Graphics®, ThreadX™ provided by Express Logic®, FreeRTOS, REX OSprovided by Qualcomm®, OKL4 provided by Open Kernel (OK) Labs®, or anyother suitable RTOS, such as those discussed herein. In addition, thebaseband circuitry 710 includes one or more audio DSPs 704F. The audioDSP(s) 704F include elements for compression/decompression and echocancellation and may include other suitable processing elements in otherembodiments.

In some embodiments, each of the processors 704A-704E include respectivememory interfaces to send/receive data to/from the memory 704G. Thebaseband circuitry 710 may further include one or more interfaces tocommunicatively couple to other circuitries/devices, such as aninterface to send/receive data to/from memory external to the basebandcircuitry 710; an application circuitry interface to send/receive datato/from the application circuitry 405/505 of FIGS. 4-7); an RF circuitryinterface to send/receive data to/from RF circuitry 706 of FIG. 7; awireless hardware connectivity interface to send/receive data to/fromone or more wireless hardware elements (e.g., NFC components,Bluetooth®/Bluetooth® Low Energy components, Wi-Fi® components, and/orthe like); and a power management interface to send/receive power orcontrol signals to/from the PMIC 525.

In alternate embodiments (which may be combined with the above describedembodiments), baseband circuitry 710 comprises one or more digitalbaseband systems, which are coupled with one another via an interconnectsubsystem and to a CPU subsystem, an audio subsystem, and an interfacesubsystem. The digital baseband subsystems may also be coupled to adigital baseband interface and a mixed-signal baseband subsystem viaanother interconnect subsystem. Each of the interconnect subsystems mayinclude a bus system, point-to-point connections, network-on-chip (NOC)structures, and/or some other suitable bus or interconnect technology,such as those discussed herein. The audio subsystem may include DSPcircuitry, buffer memory, program memory, speech processing acceleratorcircuitry, data converter circuitry such as analog-to-digital anddigital-to-analog converter circuitry, analog circuitry including one ormore of amplifiers and filters, and/or other like components. In anaspect of the present disclosure, baseband circuitry 710 may includeprotocol processing circuitry with one or more instances of controlcircuitry (not shown) to provide control functions for the digitalbaseband circuitry and/or radio frequency circuitry (e.g., the radiofront end modules 715).

Although not shown by FIG. 7, in some embodiments, the basebandcircuitry 710 includes individual processing device(s) to operate one ormore wireless communication protocols (e.g., a “multi-protocol basebandprocessor” or “protocol processing circuitry”) and individual processingdevice(s) to implement PHY layer functions. In these embodiments, thePHY layer functions include the aforementioned radio control functions.In these embodiments, the protocol processing circuitry operates orimplements various protocol layers/entities of one or more wirelesscommunication protocols. In a first example, the protocol processingcircuitry may operate LTE protocol entities and/or 5G/NR protocolentities when the baseband circuitry 710 and/or RF circuitry 706 arepart of mmWave communication circuitry or some other suitable cellularcommunication circuitry. In the first example, the protocol processingcircuitry would operate MAC, RLC, PDCP, SDAP, RRC, and NAS functions. Ina second example, the protocol processing circuitry may operate one ormore IEEE-based protocols when the baseband circuitry 710 and/or RFcircuitry 706 are part of a Wi-Fi communication system. In the secondexample, the protocol processing circuitry would operate Wi-Fi MAC andlogical link control (LLC) functions. The protocol processing circuitrymay include one or more memory structures (e.g., 704G) to store programcode and data for operating the protocol functions, as well as one ormore processing cores to execute the program code and perform variousoperations using the data. The baseband circuitry 710 may also supportradio communications for more than one wireless protocol.

The various hardware elements of the baseband circuitry 710 discussedherein may be implemented, for example, as a solder-down substrateincluding one or more integrated circuits (ICs), a single packaged ICsoldered to a main circuit board or a multi-chip module containing twoor more ICs. In one example, the components of the baseband circuitry710 may be suitably combined in a single chip or chipset, or disposed ona same circuit board. In another example, some or all of the constituentcomponents of the baseband circuitry 710 and RF circuitry 706 may beimplemented together such as, for example, a system on a chip (SoC) orSystem-in-Package (SiP). In another example, some or all of theconstituent components of the baseband circuitry 710 may be implementedas a separate SoC that is communicatively coupled with and RF circuitry706 (or multiple instances of RF circuitry 706). In yet another example,some or all of the constituent components of the baseband circuitry 710and the application circuitry 405/505 may be implemented together asindividual SoCs mounted to a same circuit board (e.g., a “multi-chippackage”).

In some embodiments, the baseband circuitry 710 may provide forcommunication compatible with one or more radio technologies. Forexample, in some embodiments, the baseband circuitry 710 may supportcommunication with an E-UTRAN or other WMAN, a WLAN, a WPAN. Embodimentsin which the baseband circuitry 710 is configured to support radiocommunications of more than one wireless protocol may be referred to asmulti-mode baseband circuitry.

RF circuitry 706 may enable communication with wireless networks usingmodulated electromagnetic radiation through a non-solid medium. Invarious embodiments, the RF circuitry 706 may include switches, filters,amplifiers, etc. to facilitate the communication with the wirelessnetwork. RF circuitry 706 may include a receive signal path, which mayinclude circuitry to down-convert RF signals received from the FEMcircuitry 708 and provide baseband signals to the baseband circuitry710. RF circuitry 706 may also include a transmit signal path, which mayinclude circuitry to up-convert baseband signals provided by thebaseband circuitry 710 and provide RF output signals to the FEMcircuitry 708 for transmission.

In some embodiments, the receive signal path of the RF circuitry 706 mayinclude mixer circuitry 706 a, amplifier circuitry 706 b and filtercircuitry 706 c. In some embodiments, the transmit signal path of the RFcircuitry 706 may include filter circuitry 706 c and mixer circuitry 706a. RF circuitry 706 may also include synthesizer circuitry 706 d forsynthesizing a frequency for use by the mixer circuitry 706 a of thereceive signal path and the transmit signal path. In some embodiments,the mixer circuitry 706 a of the receive signal path may be configuredto down-convert RF signals received from the FEM circuitry 708 based onthe synthesized frequency provided by synthesizer circuitry 706 d. Theamplifier circuitry 706 b may be configured to amplify thedown-converted signals and the filter circuitry 706 c may be a low-passfilter (LPF) or band-pass filter (BPF) configured to remove unwantedsignals from the down-converted signals to generate output basebandsignals. Output baseband signals may be provided to the basebandcircuitry 710 for further processing. In some embodiments, the outputbaseband signals may be zero-frequency baseband signals, although thisis not a requirement. In some embodiments, mixer circuitry 706 a of thereceive signal path may comprise passive mixers, although the scope ofthe embodiments is not limited in this respect.

In some embodiments, the mixer circuitry 706 a of the transmit signalpath may be configured to up-convert input baseband signals based on thesynthesized frequency provided by the synthesizer circuitry 706 d togenerate RF output signals for the FEM circuitry 708. The basebandsignals may be provided by the baseband circuitry 710 and may befiltered by filter circuitry 706 c.

In some embodiments, the mixer circuitry 706 a of the receive signalpath and the mixer circuitry 706 a of the transmit signal path mayinclude two or more mixers and may be arranged for quadraturedownconversion and upconversion, respectively. In some embodiments, themixer circuitry 706 a of the receive signal path and the mixer circuitry706 a of the transmit signal path may include two or more mixers and maybe arranged for image rejection (e.g., Hartley image rejection). In someembodiments, the mixer circuitry 706 a of the receive signal path andthe mixer circuitry 706 a of the transmit signal path may be arrangedfor direct downconversion and direct upconversion, respectively. In someembodiments, the mixer circuitry 706 a of the receive signal path andthe mixer circuitry 706 a of the transmit signal path may be configuredfor super-heterodyne operation.

In some embodiments, the output baseband signals and the input basebandsignals may be analog baseband signals, although the scope of theembodiments is not limited in this respect. In some alternateembodiments, the output baseband signals and the input baseband signalsmay be digital baseband signals. In these alternate embodiments, the RFcircuitry 706 may include analog-to-digital converter (ADC) anddigital-to-analog converter (DAC) circuitry and the baseband circuitry710 may include a digital baseband interface to communicate with the RFcircuitry 706.

In some dual-mode embodiments, a separate radio IC circuitry may beprovided for processing signals for each spectrum, although the scope ofthe embodiments is not limited in this respect.

In some embodiments, the synthesizer circuitry 706 d may be afractional-N synthesizer or a fractional N/N+1 synthesizer, although thescope of the embodiments is not limited in this respect as other typesof frequency synthesizers may be suitable. For example, synthesizercircuitry 706 d may be a delta-sigma synthesizer, a frequencymultiplier, or a synthesizer comprising a phase-locked loop with afrequency divider.

The synthesizer circuitry 706 d may be configured to synthesize anoutput frequency for use by the mixer circuitry 706 a of the RFcircuitry 706 based on a frequency input and a divider control input. Insome embodiments, the synthesizer circuitry 706 d may be a fractionalN/N+1 synthesizer.

In some embodiments, frequency input may be provided by a voltagecontrolled oscillator (VCO), although that is not a requirement. Dividercontrol input may be provided by either the baseband circuitry 710 orthe application circuitry 405/505 depending on the desired outputfrequency. In some embodiments, a divider control input (e.g., N) may bedetermined from a look-up table based on a channel indicated by theapplication circuitry 405/505.

Synthesizer circuitry 706 d of the RF circuitry 706 may include adivider, a delay-locked loop (DLL), a multiplexer and a phaseaccumulator. In some embodiments, the divider may be a dual modulusdivider (DMD) and the phase accumulator may be a digital phaseaccumulator (DPA). In some embodiments, the DMD may be configured todivide the input signal by either N or N+1 (e.g., based on a carry out)to provide a fractional division ratio. In some example embodiments, theDLL may include a set of cascaded, tunable, delay elements, a phasedetector, a charge pump and a D-type flip-flop. In these embodiments,the delay elements may be configured to break a VCO period up into Ndequal packets of phase, where Nd is the number of delay elements in thedelay line. In this way, the DLL provides negative feedback to helpensure that the total delay through the delay line is one VCO cycle.

In some embodiments, synthesizer circuitry 706 d may be configured togenerate a carrier frequency as the output frequency, while in otherembodiments, the output frequency may be a multiple of the carrierfrequency (e.g., twice the carrier frequency, four times the carrierfrequency) and used in conjunction with quadrature generator and dividercircuitry to generate multiple signals at the carrier frequency withmultiple different phases with respect to each other. In someembodiments, the output frequency may be a LO frequency (fLO). In someembodiments, the RF circuitry 706 may include an IQ/polar converter.

FEM circuitry 708 may include a receive signal path, which may includecircuitry configured to operate on RF signals received from antennaarray 711, amplify the received signals and provide the amplifiedversions of the received signals to the RF circuitry 706 for furtherprocessing. FEM circuitry 708 may also include a transmit signal path,which may include circuitry configured to amplify signals fortransmission provided by the RF circuitry 706 for transmission by one ormore of antenna elements of antenna array 711. In various embodiments,the amplification through the transmit or receive signal paths may bedone solely in the RF circuitry 706, solely in the FEM circuitry 708, orin both the RF circuitry 706 and the FEM circuitry 708.

In some embodiments, the FEM circuitry 708 may include a TX/RX switch toswitch between transmit mode and receive mode operation. The FEMcircuitry 708 may include a receive signal path and a transmit signalpath. The receive signal path of the FEM circuitry 708 may include anLNA to amplify received RF signals and provide the amplified received RFsignals as an output (e.g., to the RF circuitry 706). The transmitsignal path of the FEM circuitry 708 may include a power amplifier (PA)to amplify input RF signals (e.g., provided by RF circuitry 706), andone or more filters to generate RF signals for subsequent transmissionby one or more antenna elements of the antenna array 711.

The antenna array 711 comprises one or more antenna elements, each ofwhich is configured convert electrical signals into radio waves totravel through the air and to convert received radio waves intoelectrical signals. For example, digital baseband signals provided bythe baseband circuitry 710 is converted into analog RF signals (e.g.,modulated waveform) that will be amplified and transmitted via theantenna elements of the antenna array 711 including one or more antennaelements (not shown). The antenna elements may be omnidirectional,direction, or a combination thereof. The antenna elements may be formedin a multitude of arranges as are known and/or discussed herein. Theantenna array 711 may comprise microstrip antennas or printed antennasthat are fabricated on the surface of one or more printed circuitboards. The antenna array 711 may be formed in as a patch of metal foil(e.g., a patch antenna) in a variety of shapes, and may be coupled withthe RF circuitry 706 and/or FEM circuitry 708 using metal transmissionlines or the like.

Processors of the application circuitry 405/505 and processors of thebaseband circuitry 710 may be used to execute elements of one or moreinstances of a protocol stack. For example, processors of the basebandcircuitry 710, alone or in combination, may be used execute Layer 3,Layer 2, or Layer 1 functionality, while processors of the applicationcircuitry 405/505 may utilize data (e.g., packet data) received fromthese layers and further execute Layer 4 functionality (e.g., TCP andUDP layers). As referred to herein, Layer 3 may comprise a RRC layer,described in further detail below. As referred to herein, Layer 2 maycomprise a MAC layer, an RLC layer, and a PDCP layer, described infurther detail below. As referred to herein, Layer 1 may comprise a PHYlayer of a UE/RAN node, described in further detail infra.

FIG. 8 illustrates various protocol functions that may be implemented ina wireless communication device according to various embodiments. Inparticular, FIG. 8 includes an arrangement 800 showing interconnectionsbetween various protocol layers/entities. The following description ofFIG. 8 is provided for various protocol layers/entities that operate inconjunction with the 5G/NR system standards and LTE system standards,but some or all of the aspects of FIG. 8 may be applicable to otherwireless communication network systems as well.

The protocol layers of arrangement 800 may include one or more of PHY810, MAC 820, RLC 830, PDCP 840, SDAP 847, RRC 855, and NAS layer 857,in addition to other higher layer functions not illustrated. Theprotocol layers may include one or more service access points (e.g.,items 859, 856, 850, 849, 845, 835, 825, and 815 in FIG. 8) that mayprovide communication between two or more protocol layers.

The PHY 810 may transmit and receive physical layer signals 805 that maybe received from or transmitted to one or more other communicationdevices. The physical layer signals 805 may comprise one or morephysical channels, such as those discussed herein. The PHY 810 mayfurther perform link adaptation or adaptive modulation and coding (AMC),power control, cell search (e.g., for initial synchronization andhandover purposes), and other measurements used by higher layers, suchas the RRC 855. The PHY 810 may still further perform error detection onthe transport channels, forward error correction (FEC) coding/decodingof the transport channels, modulation/demodulation of physical channels,interleaving, rate matching, mapping onto physical channels, and MIMOantenna processing. In embodiments, an instance of PHY 810 may processrequests from and provide indications to an instance of MAC 820 via oneor more PHY-SAP 815. According to some embodiments, requests andindications communicated via PHY-SAP 815 may comprise one or moretransport channels.

Instance(s) of MAC 820 may process requests from, and provideindications to, an instance of RLC 830 via one or more MAC-SAPs 825.These requests and indications communicated via the MAC-SAP 825 maycomprise one or more logical channels. The MAC 820 may perform mappingbetween the logical channels and transport channels, multiplexing of MACSDUs from one or more logical channels onto TBs to be delivered to PHY810 via the transport channels, de-multiplexing MAC SDUs to one or morelogical channels from TBs delivered from the PHY 810 via transportchannels, multiplexing MAC SDUs onto TBs, scheduling informationreporting, error correction through HARQ, and logical channelprioritization.

Instance(s) of RLC 830 may process requests from and provide indicationsto an instance of PDCP 840 via one or more radio link control serviceaccess points (RLC-SAP) 835. These requests and indications communicatedvia RLC-SAP 835 may comprise one or more RLC channels. The RLC 830 mayoperate in a plurality of modes of operation, including: TransparentMode™, Unacknowledged Mode (UM), and Acknowledged Mode (AM). The RLC 830may execute transfer of upper layer protocol data units (PDUs), errorcorrection through automatic repeat request (ARQ) for AM data transfers,and concatenation, segmentation and reassembly of RLC SDUs for UM and AMdata transfers. The RLC 830 may also execute re-segmentation of RLC dataPDUs for AM data transfers, reorder RLC data PDUs for UM and AM datatransfers, detect duplicate data for UM and AM data transfers, discardRLC SDUs for UM and AM data transfers, detect protocol errors for AMdata transfers, and perform RLC re-establishment.

Instance(s) of PDCP 840 may process requests from and provideindications to instance(s) of RRC 855 and/or instance(s) of SDAP 847 viaone or more packet data convergence protocol service access points(PDCP-SAP) 845. These requests and indications communicated via PDCP-SAP845 may comprise one or more radio bearers. The PDCP 840 may executeheader compression and decompression of IP data, maintain PDCP SequenceNumbers (SNs), perform in-sequence delivery of upper layer PDUs atre-establishment of lower layers, eliminate duplicates of lower layerSDUs at re-establishment of lower layers for radio bearers mapped on RLCAM, cipher and decipher control plane data, perform integrity protectionand integrity verification of control plane data, control timer-baseddiscard of data, and perform security operations (e.g., ciphering,deciphering, integrity protection, integrity verification, etc.).

Instance(s) of SDAP 847 may process requests from and provideindications to one or more higher layer protocol entities via one ormore SDAP-SAP 849. These requests and indications communicated viaSDAP-SAP 849 may comprise one or more QoS flows. The SDAP 847 may mapQoS flows to DRBs, and vice versa, and may also mark QFIs in DL and ULpackets. A single SDAP entity 847 may be configured for an individualPDU session. In the UL direction, the NG-RAN 110 may control the mappingof QoS Flows to DRB(s) in two different ways, reflective mapping orexplicit mapping. For reflective mapping, the SDAP 847 of a UE 101 maymonitor the QFIs of the DL packets for each DRB, and may apply the samemapping for packets flowing in the UL direction. For a DRB, the SDAP 847of the UE 101 may map the UL packets belonging to the QoS flows(s)corresponding to the QoS flow ID(s) and PDU session observed in the DLpackets for that DRB. To enable reflective mapping, the NG-RAN 310 maymark DL packets over the Uu interface with a QoS flow ID. The explicitmapping may involve the RRC 855 configuring the SDAP 847 with anexplicit QoS flow to DRB mapping rule, which may be stored and followedby the SDAP 847. In embodiments, the SDAP 847 may only be used in NRimplementations and may not be used in LTE implementations.

The RRC 855 may configure, via one or more management service accesspoints (M-SAP), aspects of one or more protocol layers, which mayinclude one or more instances of PHY 810, MAC 820, RLC 830, PDCP 840 andSDAP 847. In embodiments, an instance of RRC 855 may process requestsfrom and provide indications to one or more NAS entities 857 via one ormore RRC-SAPs 856. The main services and functions of the RRC 855 mayinclude broadcast of system information (e.g., included in MIBs or SIBsrelated to the NAS), broadcast of system information related to theaccess stratum (AS), paging, establishment, maintenance and release ofan RRC connection between the UE 101 and RAN 110 (e.g., RRC connectionpaging, RRC connection establishment, RRC connection modification, andRRC connection release), establishment, configuration, maintenance andrelease of point to point Radio Bearers, security functions includingkey management, inter-RAT mobility, and measurement configuration for UEmeasurement reporting. The MIBs and SIBs may comprise one or more IEs,which may each comprise individual data fields or data structures.

According to various embodiments, RRC 855 is used to configure UEspecific PDSCH parameters and/or PUSCH parameters. For example, the RRC855 of a RAN node 111 may transmit a suitable RRC message (e.g., an RRCconnection establishment message, RRC connection reconfigurationmessage, or the like) to the UE 101, where the RRC message includes oneor more IEs, which is a structural element containing one or more fieldswhere each field includes parameters, content, and/or data. Theparameters, content, and/or data included in the one or more fields ofthe IEs are used to configure the UE 101 to operate in a particularmanner. In some embodiments, a PDSCH configuration (PDSCH-Config) IE isused to configure UE specific PDSCH parameters, and a PUSCHconfiguration (PUSCH-Config) IE is used to configure UE specific PUSCHparameters applicable to a particular BWP. An example PDSCH-Config IE isshown by table 20 and table 21 shows field descriptions for the fieldsof the PDSCH-Config IE. An example PUSCH-Config IE is shown by table 22and table 23 shows the field descriptions for the fields of thePDSCH-Config IE.

TABLE 20 PDSCH-Config information element -- ASN1START --TAG-PDSCH-CONFIG-START PDSCH-Config ::= SEQUENCE {dataScramblingIdentityPDSCH INTEGER (0..1023) OPTIONAL, -- Need Sdmrs-DownlinkForPDSCH-MappingTypeA SetupRelease { DMRS- DownlinkConfig }OPTIONAL, -- Need M dmrs-DownlinkForPDSCH-MappingTypeB SetupRelease {DMRS- DownlinkConfig } OPTIONAL, -- Need M tci-StatesToAddModListSEQUENCE (SIZE(1..maxNrofTCI- States)) OF TCI-State  OPTIONAL, -- Need Ntci-StatesToReleaseList SEQUENCE (SIZE(1..maxNrofTCI- States)) OFTCI-StateId  OPTIONAL, -- Need N vrb-ToPRB-Interleaver ENUMERATED {n2,n4} OPTIONAL, -- Need S resourceAllocation ENUMERATED {resourceAllocationType0, resourceAllocationType1, dynamicSwitch},pdsch-TimeDomainAllocationList SetupRelease { PDSCH-TimeDomainResourceAllocationList } OPTIONAL, -- Need Mpdsch-AggregationFactor ENUMERATED { n2, n4, n8 } OPTIONAL, -- Need SrateMatchPatternToAddModList SEQUENCE (SIZE(1..maxNrofRateMatchPatterns)) OF RateMatchPattern OPTIONAL, -- Need NrateMatchPatternToReleaseList SEQUENCE (SIZE(1..maxNrofRateMatchPatterns)) OF RateMatchPatternId OPTIONAL, -- Need NrateMatchPatternGroup1 RateMatchPatternGroup OPTIONAL, -- Need RrateMatchPatternGroup2 RateMatchPatternGroup OPTIONAL, -- Need Rrbg-Size ENUMERATED {config1, config2}, mcs-Table ENUMERATED {qam256,qam64LowSE} OPTIONAL, -- Need S maxNrofCodeWordsScheduledByDCIENUMERATED {n1, n2} OPTIONAL, -- Need R prb-BundlingType CHOICE {staticBundling  SEQUENCE { bundleSize ENUMERATED { n4, wideband }OPTIONAL -- Need S }, dynamicBundling SEQUENCE { bundleSizeSet1ENUMERATED { n4, wideband, n2-wideband, n4-wideband } OPTIONAL, -- NeedS bundleSizeSet2 ENUMERATED { n4, wideband } OPTIONAL -- Need S } },zp-CSI-RS-ResourceToAddModList SEQUENCE (SIZE(1..maxNrofZP-CSI-RS-Resources)) OF ZP-CSI-RS-Resource OPTIONAL, -- NeedN zp-CSI-RS-ResourceToReleaseList SEQUENCE (SIZE(1..maxNrofZP-CSI-RS-Resources)) OF ZP-CSI-RS-ResourceId OPTIONAL, --Need N aperiodic-ZP-CSI-RS-ResourceSetsToAddModList SEQUENCE (SIZE(1..maxNrofZP-CSI-RS-ResourceSets)) OF ZP-CSI-RS-ResourceSet OPTIONAL,-- Need N aperiodic-ZP-CSI-RS-ResourceSetsToReleaseList SEQUENCE (SIZE(1..maxNrofZP-CSI-RS-ResourceSets)) OF ZP-CSI-RS-ResourceSetId OPTIONAL,-- NeedN sp-ZP-CSI-RS-ResourceSetsToAddModList SEQUENCE (SIZE(1..maxNrofZP- CSI-RS-ResourceSets)) OF ZP-CSI-RS-ResourceSetOPTIONAL, -- Need N sp-ZP-CSI-RS-ResourceSetsToReleaseList SEQUENCE(SIZE (1..maxNrofZP- CSI-RS-ResourceSets)) OF ZP-CSI-RS-ResourceSetIdOPTIONAL, -- Need N p-ZP-CSI-RS-ResourceSet SetupRelease { ZP-CSI-RS-ResourceSet }  OPTIONAL, -- Need M ... } RateMatchPatternGroup ::=SEQUENCE (SIZE (1..maxNrofRateMatchPatternsPerGroup)) OF CHOICE {cellLevel RateMatchPatternId, bwpLevel RateMatchPatternId } --TAG-PDSCH-CONFIG-STOP -- ASN1STOP

TABLE 21 PDSCH-Config field descriptionsaperiodic-ZP-CSI-RS-ResourceSetsToAddModList AddMod/Release lists forconfiguring aperiodically triggered zero-power CSI-RS resource sets.Each set contains a ZP-CSI-RS-ResourceSetId and the IDs of one or moreZP-CSI-RS-Resources (the actual resources are defined in thezp-CSI-RS-ResourceToAddModList). The network configures the UE with atmost 3 aperiodic ZP-CSI-RS- ResourceSets and it uses only theZP-CSI-RS-ResourceSetId 1 to 3. The network triggers a set by indicatingits ZP-CSI-RS-ResourceSetId in the DCI payload. The DCI codepoint ‘01’triggers the resource set with ZP-CSI-RS- ResourceSetId 1, the DCIcodepoint ‘10’ triggers the resource set with ZP-CSI-RS-ResourceSetId 2,and the DCI codepoint ‘11’ triggers the resource set withZP-CSI-RS-ResourceSetId 3. Corresponds to L1 parameter‘Aperiodic-ZP-CSI-RS-Resource-List’. dataScramblingIdentityPDSCHIdentifier used to initialize data scrambling (c_init) for PDSCH. If thefield is absent, the UE applies the physical cell ID.dmrs-DownlinkForPDSCH-MappingTypeA DMRS configuration for PDSCHtransmissions using PDSCH mapping type A (chosen dynamically via PDSCH-TimeDomainResourceAllocation). Only the fields dmrs-Type,dmrs-AdditionalPosition and maxLength may be set differently for mappingtype A and B. dmrs-DownlinkForPDSCH-MappingTypeB DMRS configuration forPDSCH transmissions using PDSCH mapping type B (chosen dynamically viaPDSCH- TimeDomainResourceAllocation). Only the fields dmrs-Type,dmrs-AdditionalPosition and maxLength may be set differently for mappingtype A and B. maxNrofCodeWordsScheduledByDCI Maximum number of codewords that a single DCI may schedule. This changes the number ofMCS/RV/NDI bits in the DCI message from 1 to 2. mcs-Table Indicateswhich MCS table the UE shall use for PDSCH. If the field is absent theUE applies the value 64QAM. pdsch-AggregationFactor Number ofrepetitions for data. Corresponds to L1 parameter‘aggregation-factor-DL’. When the field is absent the UE applies thevalue 1 pdsch-TimeDomainAllocationList List of time-domainconfigurations for timing of DL assignment to DL data. If configured,the values provided herein override the values received in correspondingPDSCH-ConfigCommon for PDCCH scrambled with C-RNTI or CS-RNTI but notfor CORESET#0 for which the default values in table 3 apply.prb-BundlingType Indicates the PRB bundle type and bundle size(s).Corresponds to L1 parameter ‘PRB_bundling’. If dynamic is chosen, theactual bundleSizeSet1 or bundleSizeSet2 to use is indicated via DCI.Constraints on bundleSize(Set) setting depending onvrb-ToPRB-Interleaver and rbg-Size settings. If a bundleSize(Set) valueis absent, the UE applies the value n2. p-ZP-CSI-RS-ResourceSet A set ofperiodically occurring ZP-CSI-RS-Resources (the actual resources aredefined in the zp-CSI-RS- ResourceToAddModList). The network uses theZP-CSI-RS-ResourceSetId = 0 for this set. rateMatchPatternGroup1 The IDsof a first group of RateMatchPatterns defined inPDSCH-Config->rateMatchPatternToAddModList (BWP level) or inServingCellConfig ->rateMatchPatternToAddModList (cell level). Thesepatterns can be activated dynamically by DCI. Corresponds to L1parameter ‘Resource-set-group-1’. rateMatchPatternGroup2 The IDs of asecond group of RateMatchPatterns defined inPDSCH-Config->rateMatchPatternToAddModList (BWP level) or inServingCellConfig ->rateMatchPatternToAddModList (cell level). Thesepatterns can be activated dynamically by DCI. Corresponds to L1parameter ‘Resource-set-group-2’. rateMatchPatternToAddModList Resourcespatterns which the UE should rate match PDSCH around. The UE ratematches around the union of all resources indicated in the nestedbitmaps. Corresponds to L1 parameter ‘Resource-set-BWP’. There may be aset of patterns per cell and one per BWP. rbg-Size Selection betweenconfig 1 and config 2 for RBG size for PDSCH. The NW may only set thefield to config2 if resourceAllocation is set to resourceAllocationType0or dynamicSwitch. Corresponds to L1 parameter ‘RBG-size- PDSCH’.resourceAllocation Configuration of resource allocation type 0 andresource allocation type 1 for non-fallback DCI Corresponds to L1parameter ‘Resouce-allocation-config’.sp-ZP-CSI-RS-ResourceSetsToAddModList AddMod/Release lists forconfiguring semi-persistent zero-power CSI-RS resource sets. Each setcontains a ZP- CSI-RS-ResourceSetId and the IDs of one or moreZP-CSI-RS-Resources (the actual resources are defined in thezp-CSI-RS-ResourceToAddModList). Corresponds to L1 parameter‘ZP-CSI-RS-ResourceSetConfigList’. tci-StatesToAddModList A list ofTransmission Configuration Indicator (TCI) states indicating atransmission configuration which includes QCL-relationships between theDL RSs in one RS set and the PDSCH DMRS ports. vrb-ToPRB-InterleaverInterleaving unit configurable between 2 and 4 PRBs Corresponds to L1parameter ‘VRB-to-PRB-interleaver’. When the field is absent, the UEperforms non-interleaved VRB-to-PRB mapping.zp-CSI-RS-ResourceToAddModList A list of Zero-Power (ZP) CSI-RSresources used for PDSCH rate-matching. Each resource in this list maybe referred to from only one type of resource set, i.e., aperiodic,semi-persistent or periodic.

TABLE 22 PUSCH-Config information element -- ASN1START --TAG-PUSCH-CONFIG-START PUSCH-Config ::= SEQUENCE {dataScramblingIdentityPUSCH INTEGER (0..1023) OPTIONAL, -- Need StxConfig ENUMERATED {codebook, nonCodebook}  OPTIONAL, -- Need Sdmrs-UplinkForPUSCH-MappingTypeA SetupRelease { DMRS-UplinkConfig } OPTIONAL, -- Need M dmrs-UplinkForPUSCH-MappingTypeB SetupRelease {DMRS-UplinkConfig }  OPTIONAL, -- Need M pusch-PowerControlPUSCH-PowerControl OPTIONAL, -- Need M frequencyHopping ENUMERATED{intraSlot, interSlot} OPTIONAL, -- Need S frequencyHoppingOffsetListsSEQUENCE (SIZE (1..4)) OF INTEGER (1.. maxNrofPhysicalResourceBlocks-1) OPTIONAL, -- Need M resourceAllocation ENUMERATED {resourceAllocationType0, resourceAllocationType1, dynamicSwitch},pusch-TimeDomainAllocationList SetupRelease { PUSCH-TimeDomainResourceAllocationList } OPTIONAL, -- Need Mpusch-AggregationFactor ENUMERATED { n2, n4, n8 } OPTIONAL, -- Need Smcs-Table ENUMERATED {qam256, qam64LowSE} OPTIONAL, -- Need Smcs-TableTransformPrecoder ENUMERATED {qam256, qam64LowSE} OPTIONAL, --Need S transformPrecoder ENUMERATED {enabled, disabled} OPTIONAL, --Need S codebookSubset ENUMERATED {fullyAndPartialAndNonCoherent,partialAndNonCoherent, nonCoherent} OPTIONAL, -- Cond codebookBasedmaxRank INTEGER (1..4) OPTIONAL, -- Cond codebookBased rbg-SizeENUMERATED { config2} OPTIONAL, -- Need S uci-OnPUSCH SetupRelease {UCI-OnPUSCH} OPTIONAL, -- Need M tp-pi2BPSK ENUMERATED {enabled}OPTIONAL, -- Need S ... } UCI-OnPUSCH ::= SEQUENCE { betaOffsets CHOICE{ dynamic SEQUENCE (SIZE (4)) OF BetaOffsets, semiStatic BetaOffsets }OPTIONAL, -- Need M scaling ENUMERATED { f0p5, f0p65, f0p8, f1 } } --TAG-PUSCH-CONFIG-STOP -- ASN1STOP

TABLE 23 PUSCH-Config field descriptions codebookSubset Subset of PMIsaddressed by TPMI, where PMIs are those supported by UEs with maximumcoherence capabilities Corresponds to L1 parameter ‘ULCodebookSubset’.dataScramblingIdentityPUSCH Identifier used to initiate data scrambling(c_init) for PUSCH. If the field is absent, the UE applies the physicalcell ID. dmrs-UplinkForPUSCH-MappingTypeA DMRS configuration for PUSCHtransmissions using PUSCH mapping type A (chosen dynamically via PUSCH-TimeDomainResourceAllocation). Only the fields dmrs-Type,dmrs-AdditionalPosition and maxLength may be set differently for mappingtype A and B. dmrs-UplinkForPUSCH-MappingTypeB DMRS configuration forPUSCH transmissions using PUSCH mapping type B (chosen dynamically viaPUSCH- TimeDomainResourceAllocation). Only the fields dmrs-Type,dmrs-AdditionalPosition and maxLength may be set differently for mappingtype A and B. frequencyHopping The value intraSlot enables ‘Intra-slotfrequency hopping’ and the value interSlot enables ‘Inter-slot frequencyhopping’. If the field is absent, frequency hopping is not configured.Corresponds to L1 parameter ‘Frequency- hopping-PUSCH’.frequencyHoppingOffsetLists Set of frequency hopping offsets used whenfrequency hopping is enabled for granted transmission (not msg3) andtype 2 Corresponds to L1 parameter ‘Frequency-hopping-offsets-set’.maxRank Subset of PMIs addressed by TRIs from 1 to ULmaxRank.Corresponds to L1 parameter ‘ULmaxRank’. mcs-Table Indicates which MCStable the UE shall use for PUSCH without transform precoder (see 38.214,section 6.1.4.1). If the field is absent the UE applies the value 64QAMmcs-TableTransformPrecoder Indicates which MCS table the UE shall usefor PUSCH with transform precoding. If the field is absent the UEapplies the value 64QAM pusch-AggregationFactor Number of repetitionsfor data. Corresponds to L1 parameter ‘aggregation-factor-UL’. If thefield is absent the UE applies the value 1.pusch-TimeDomainAllocationList List of time domain allocations fortiming of UL assignment to UL data. If configured, the values providedherein override the values received in corresponding PUSCH-ConfigCommonfor PDCCH scrambled with C-RNTI or CS-RNTI but not for CORESET#0 (seetable 9). rbg-Size Selection between configuration 1 and configuration 2for RBG size for PUSCH. When the field is absent the UE applies thevalue config1. The NW may only set the field to config2 ifresourceAllocation is set to resourceAllocationType0 or dynamicSwitch.Corresponds to L1 parameter ‘RBG-size-PUSCH’. resourceAllocationConfiguration of resource allocation type 0 and resource allocation type1 for non-fallback DCI Corresponds to L1 parameter‘Resouce-allocation-config’. tp-pi2BPSK Enables pi/2-BPSK modulationwith transform precoding if the field is present and disables itotherwise. transformPrecoder The UE specific selection of transformerprecoder for PUSCH. When the field is absent the UE applies the valuemsg3-tp. Corresponds to L1 parameter ‘PUSCH-tp’. txConfig Whether UEuses codebook based or non-codebook based transmission. Corresponds toL1 parameter ‘ulTxConfig’. If the field is absent, the UE transmitsPUSCH on one antenna port. betaOffsets Selection between andconfiguration of dynamic and semi-static beta-offset. If the field isabsent or released, the UE applies the value ‘semiStatic’ and theBetaOffsets according to [BetaOffsets]. Corresponds to L1 parameter‘UCI-on-PUSCH’. scaling Indicates a scaling factor to limit the numberof resource elements assigned to UCI on PUSCH. Value f0p5 corresponds to0.5, value f0p65 corresponds to 0.65, and so on. The value configuredherein is applicable for PUCCH with configured grant. Corresponds to L1parameter ‘uci-on-pusch-scaling’.

In another embodiment, a PDSCH common configuration (PDSCH-ConfigCommon)IE is used to configure UE specific PDSCH parameters, and a PUSCH commonconfiguration (PUSCH-ConfigCommon) IE is used to configure UE specificPUSCH parameters. An example PDSCH-ConfigCommon IE is shown by table 24and table 25 shows field descriptions for the fields of thePDSCH-ConfigCommon IE. An example PUSCH-ConfigCommon IE is shown bytable 26 and table 27 shows field descriptions for the fields of thePUSCH-ConfigCommon IE.

TABLE 24 PDSCH-ConfigCommon information element -- ASN1START --TAG-PDSCH-CONFIGCOMMON-START PDSCH-ConfigCommon ::= SEQUENCE {pdsch-TimeDomainAllocationList PDSCH- TimeDomainResourceAllocationListOPTIONAL, -- Need R ... } -- TAG-PDSCH-CONFIGCOMMON-STOP -- ASN1STOP

TABLE 25 PDSCH-ConfigCommon.field descriptionspdsch-AllocationListAllocationList List of time-domain configurationsfor timing of DL assignment to DL data. The configuration applies forPDCCH scrambled with C-RNTI or CS-RNTI but not for CORESET#0 for whichthe default values in table 3 apply.

TABLE 26 PUSCH-Config information element -- ASN1START --TAG-PUSCH-CONFIGCOMMON-START PUSCH-ConfigCommon ::= SEQUENCE {groupHoppingEnabledTransformPrecoding ENUMERATED {enabled} OPTIONAL, --Need R pusch-TimeDomainAllocationList PUSCH-TimeDomainResourceAllocationList OPTIONAL, -- Need R msg3-DeltaPreambleINTEGER (−1..6) OPTIONAL, -- Need R p0-NominalWithGrant INTEGER(−202..24) OPTIONAL, -- Need R ... } -- TAG-PUSCH-CONFIGCOMMON-STOP --ASN1STOP

TABLE 27 PUSCH-ConfigCommon field descriptionsgroupHoppingEnabledTransformPrecoding Sequence-group hopping can beenabled or disabled by means of this cell-specific parameter.Corresponds to L1 parameter ‘Group-hopping-enabled-Transform-precoding’. This field is Cell specificmsg3-DeltaPreamble Power offset between msg3 and RACH preambletransmission. Actual value = field value *2 [dB]. Corresponds to L1parameter ‘Delta-preamble-msg3’. p0-NominalWithGrant P0 value for PUSCHwith grant (except msg3). Value in dBm. Only even values (step size 2)allowed. Corresponds to L1 parameter ‘p0-nominal- pusch-withgrant’. Thisfield is cell specific pusch-TimeDomainAllocationList List of timedomain allocations for timing of UL assignment to UL data

In the examples of tables 18-19 and 22-23, thepdsch-TimeDomainAllocationList field includes a list of time-domainconfigurations for timing of DL assignment to DL data (e.g., one or morePDSCH-TimeDomainResourceAllocations). Each of these time-domainconfigurations includes or indicates a slot offset K₀, a PDSCH mappingtype, and the SLIV as discussed previously with respect to FIG. 1. Invarious embodiments, the UE 101 uses each of the time-domainconfigurations to build a time domain resource allocation table (alsoreferred to as an “RRC configured table” or the like) from which the UE101 determines a PDSCH resource allocation in the time domain based on arow index indicated by a DCI.

Table 28 shows an example PDSCH-TimeDomainResourceAllocation IE, andtable 29 shows field descriptions for the fields of thePDSCH-TimeDomainResourceAllocation IE. ThePDSCH-TimeDomainResourceAllocation IE is used to configure a time domainrelation between the PDCCH and the PDSCH. ThePDSCH-TimeDomainResourceAllocationList IE as shown by tables 18 and 22contains one or more of such PDSCH-TimeDomainResourceAllocations.

TABLE 28 PDSCH-TimeDomainResourceAllocationList information element --ASN1START -- TAG-PDSCH-TIMEDOMAINRESOURCEALLOCATIONLIST-STARTPDSCH-TimeDomainResourceAllocationList ::= SEQUENCE (SIZE(1..maxNrofDL-Allocations)) OF PDSCH-TimeDomainResourceAllocationPDSCH-TimeDomainResourceAllocation ::= SEQUENCE { k0 INTEGER(0..32)OPTIONAL, -- Need S mappingType ENUMERATED {typeA, typeB},startSymbolAndLength INTEGER (0..127) } --TAG-PDSCH-TIMEDOMAINRESOURCEALLOCATIONLIST-STOP -- ASN1STOP

TABLE 29 PDSCH-TimeDomainResourceAllocation field descriptions k0 The n1corresponds to the value 1, n2 corresponds to value 2, and so on.Corresponds to L1 parameter ‘K0’. When the field is absent the UEapplies the value 0. mappingType PDSCH mapping type.startSymbolAndLength An index giving valid combinations of start symboland length (jointly encoded) as start and length indicator (SLIV). Thenetwork configures the field so that the allocation does not cross theslot boundary. Corresponds to L1 parameter ‘Index-start-len’.

In this example, the network (e.g., a RAN node 111) indicates in the DLassignment which of the configured time domain allocations the UE 101 isto apply for that DL assignment. The UE 101 determines the bit width ofthe DCI field based on the number of entries in thePDSCH-TimeDomainResourceAllocationList. In this example, value 0 in theDCI field refers to the first element in this list, value 1 in the DCIfield refers to the second element in this list, and so on. For example,the time domain resource assignment field value m of a received DCIprovides a row index m+1 to the allocation table where the rowcorresponding to the row index m+1 refers to the m-thPDSCH-TimeDomainResourceAllocation IE in thePDSCH-TimeDomainResourceAllocationList IE.

In the examples of tables 20-21 and 24-25, thepusch-TimeDomainAllocationList field includes a list of time domainallocations for timing of UL assignment to UL data (e.g., one or morePUSCH-TimeDomainResourceAllocations). Each of these time-domainconfigurations includes or indicates a slot offset K₂, a PUSCH mappingtype, and the SLIV as discussed previously with respect to FIG. 1. Invarious embodiments, the UE 101 uses each of these time-domainconfigurations to build a time domain resource allocation table (alsoreferred to as an “RRC configured table” or the like) from which the UE101 determines a PUSCH resource allocation in the time domain based on arow index indicated by a DCI.

Table 40 shows an example PUSCH-TimeDomainResourceAllocation IE, andtable 41 shows field descriptions for the fields of thePUSCH-TimeDomainResourceAllocation IE. ThePUSCH-TimeDomainResourceAllocation IE is used to configure a time domainrelation between PDCCH and PUSCH. ThePUSCH-TimeDomainResourceAllocationList IE contains one or more of suchPUSCH-TimeDomainResourceAllocations.

TABLE 40 PDSCH-TimeDomainResourceAllocationList information element --ASN1START -- TAG-PUSCH-TIMEDOMAINRESOURCEALLOCATIONLIST-STARTPUSCH-TimeDomainResourceAllocationList ::=  SEQUENCE (SIZE(1..maxNrofUL-Allocations)) OF PUSCH-TimeDomainResourceAllocationPUSCH-TimeDomainResourceAllocation ::= SEQUENCE { k2 INTEGER(0..32)OPTIONAL, -- Need S mappingType ENUMERATED {typeA, typeB},startSymbolAndLength INTEGER (0..127) } --TAG-PUSCH-TIMEDOMAINRESOURCEALLOCATIONLIST-STOP -- ASN1STOP

TABLE 41 PUSCH-TimeDomainResourceAllocationList field descriptions k2Corresponds to L1 parameter ‘K2’. When the field is absent the UEapplies the value 1 when PUSCH SCS is 15/30 KHz; 2 when PUSCH SCS is 60KHz and 3 when PUSCH SCS is 120 KHz. mappingType Mapping type.Corresponds to L1 parameter ‘Mapping-type’. startSymbolAndLength Anindex giving valid combinations of start symbol and length (jointlyencoded) as start and length indicator (SLIV). The network configuresthe field so that the allocation does not cross the slot boundary.

In this example, the network (e.g., a RAN node 111) indicates in the ULgrant which of the configured time domain allocations the UE 101 is toapply for that UL grant. The UE 101 determines the bit width of the DCIfield based on the number of entries in thePUSCH-TimeDomainResourceAllocationList. In this example, value 0 in theDCI field refers to the first element in this list, value 1 in the DCIfield refers to the second element in this list, and so on. For example,the time domain resource assignment field value m of a received DCIprovides a row index m+1 to the allocation table where the rowcorresponding to the row index m+1 refers to the m-thPUSCH-TimeDomainResourceAllocation IE in thePUSCH-TimeDomainResourceAllocationList IE.

The NAS 857 may form the highest stratum of the control plane betweenthe UE 101 and the AMF 321. The NAS 857 may support the mobility of theUEs 101 and the session management procedures to establish and maintainIP connectivity between the UE 101 and a P-GW in LTE systems.

According to various embodiments, one or more protocol entities ofarrangement 800 may be implemented in UEs 101, RAN nodes 111, AMF 321 inNR implementations or MME 221 in LTE implementations, UPF 302 in NRimplementations or S-GW 222 and P-GW 223 in LTE implementations, or thelike to be used for control plane or user plane communications protocolstack between the aforementioned devices. In such embodiments, one ormore protocol entities that may be implemented in one or more of UE 101,gNB 111, AMF 321, etc. may communicate with a respective peer protocolentity that may be implemented in or on another device using theservices of respective lower layer protocol entities to perform suchcommunication. In some embodiments, a gNB-CU of the gNB 111 may host theRRC 855, SDAP 847, and PDCP 840 of the gNB that controls the operationof one or more gNB-DUs, and the gNB-DUs of the gNB 111 may each host theRLC 830, MAC 820, and PHY 810 of the gNB 111.

In a first example, a control plane protocol stack may comprise, inorder from highest layer to lowest layer, NAS 857, RRC 855, PDCP 840,RLC 830, MAC 820, and PHY 810. In this example, upper layers 860 may bebuilt on top of the NAS 857, which includes an IP layer 861, an SCTP862, and an application layer signaling protocol (AP) 863.

In NR implementations, the AP 863 may be an NG application protocollayer (NGAP or NG-AP) 863 for the NG interface 113 defined between theNG-RAN node 111 and the AMF 321, or the AP 863 may be an Xn applicationprotocol layer (XnAP or Xn-AP) 863 for the Xn interface 112 that isdefined between two or more RAN nodes 111.

The NG-AP 863 may support the functions of the NG interface 113 and maycomprise Elementary Procedures (EPs). An NG-AP EP may be a unit ofinteraction between the NG-RAN node 111 and the AMF 321. The NG-AP 863services may comprise two groups: UE-associated services (e.g., servicesrelated to a UE 101) and non-UE-associated services (e.g., servicesrelated to the whole NG interface instance between the NG-RAN node 111and AMF 321). These services may include functions including, but notlimited to: a paging function for the sending of paging requests toNG-RAN nodes 111 involved in a particular paging area; a UE contextmanagement function for allowing the AMF 321 to establish, modify,and/or release a UE context in the AMF 321 and the NG-RAN node 111; amobility function for UEs 101 in ECM-CONNECTED mode for intra-system HOsto support mobility within NG-RAN and inter-system HOs to supportmobility from/to EPS systems; a NAS Signaling Transport function fortransporting or rerouting NAS messages between UE 101 and AMF 321; a NASnode selection function for determining an association between the AMF321 and the UE 101; NG interface management function(s) for setting upthe NG interface and monitoring for errors over the NG interface; awarning message transmission function for providing means to transferwarning messages via NG interface or cancel ongoing broadcast of warningmessages; a Configuration Transfer function for requesting andtransferring of RAN configuration information (e.g., SON information,performance measurement (PM) data, etc.) between two RAN nodes 111 viaCN 120; and/or other like functions.

The XnAP 863 may support the functions of the Xn interface 112 and maycomprise XnAP basic mobility procedures and XnAP global procedures. TheXnAP basic mobility procedures may comprise procedures used to handle UEmobility within the NG RAN 111 (or E-UTRAN 210), such as handoverpreparation and cancellation procedures, SN Status Transfer procedures,UE context retrieval and UE context release procedures, RAN pagingprocedures, dual connectivity related procedures, and the like. The XnAPglobal procedures may comprise procedures that are not related to aspecific UE 101, such as Xn interface setup and reset procedures, NG-RANupdate procedures, cell activation procedures, and the like.

In LTE implementations, the AP 863 may be an S1 Application Protocollayer (S1-AP) 863 for the S1 interface 113 defined between an E-UTRANnode 111 and an MME, or the AP 863 may be an X2 application protocollayer (X2AP or X2-AP) 863 for the X2 interface 112 that is definedbetween two or more E-UTRAN nodes 111.

The S1 Application Protocol layer (S1-AP) 863 may support the functionsof the S1 interface, and similar to the NG-AP discussed previously, theS1-AP may comprise S1-AP EPs. An S1-AP EP may be a unit of interactionbetween the E-UTRAN node 111 and an MME 221 within an LTE CN 120. TheS1-AP 863 services may comprise two groups: UE-associated services andnon UE-associated services. These services perform functions including,but not limited to: E-UTRAN Radio Access Bearer (E-RAB) management, UEcapability indication, mobility, NAS signaling transport, RANInformation Management (RIM), and configuration transfer.

The X2AP 863 may support the functions of the X2 interface 112 and maycomprise X2AP basic mobility procedures and X2AP global procedures. TheX2AP basic mobility procedures may comprise procedures used to handle UEmobility within the E-UTRAN 120, such as handover preparation andcancellation procedures, SN Status Transfer procedures, UE contextretrieval and UE context release procedures, RAN paging procedures, dualconnectivity related procedures, and the like. The X2AP globalprocedures may comprise procedures that are not related to a specific UE101, such as X2 interface setup and reset procedures, load indicationprocedures, error indication procedures, cell activation procedures, andthe like.

The SCTP layer (alternatively referred to as the SCTP/IP layer) 862 mayprovide guaranteed delivery of application layer messages (e.g., NGAP orXnAP messages in NR implementations, or S1-AP or X2AP messages in LTEimplementations). The SCTP 862 may ensure reliable delivery of signalingmessages between the RAN node 111 and the AMF 321/MME 221 based, inpart, on the IP protocol, supported by the IP 861. The Internet Protocollayer (IP) 861 may be used to perform packet addressing and routingfunctionality. In some implementations the IP layer 861 may usepoint-to-point transmission to deliver and convey PDUs. In this regard,the RAN node 111 may comprise L2 and L1 layer communication links (e.g.,wired or wireless) with the MME/AMF to exchange information.

In a second example, a user plane protocol stack may comprise, in orderfrom highest layer to lowest layer, SDAP 847, PDCP 840, RLC 830, MAC820, and PHY 810. The user plane protocol stack may be used forcommunication between the UE 101, the RAN node 111, and UPF 302 in NRimplementations or an S-GW 222 and P-GW 223 in LTE implementations. Inthis example, upper layers 851 may be built on top of the SDAP 847, andmay include a user datagram protocol (UDP) and IP security layer(UDP/IP) 852, a General Packet Radio Service (GPRS) Tunneling Protocolfor the user plane layer (GTP-U) 853, and a User Plane PDU layer (UPPDU) 863.

The transport network layer 854 (also referred to as a “transportlayer”) may be built on IP transport, and the GTP-U 853 may be used ontop of the UDP/IP layer 852 (comprising a UDP layer and IP layer) tocarry user plane PDUs (UP-PDUs). The IP layer (also referred to as the“Internet layer”) may be used to perform packet addressing and routingfunctionality. The IP layer may assign IP addresses to user data packetsin any of IPv4, IPv6, or PPP formats, for example.

The GTP-U 853 may be used for carrying user data within the GPRS corenetwork and between the radio access network and the core network. Theuser data transported can be packets in any of IPv4, IPv6, or PPPformats, for example. The UDP/IP 852 may provide checksums for dataintegrity, port numbers for addressing different functions at the sourceand destination, and encryption and authentication on the selected dataflows. The RAN node 111 and the S-GW 222 may utilize an S1-U interfaceto exchange user plane data via a protocol stack comprising an L1 layer(e.g., PHY 810), an L2 layer (e.g., MAC 820, RLC 830, PDCP 840, and/orSDAP 847), the UDP/IP layer 852, and the GTP-U 853. The S-GW 222 and theP-GW 223 may utilize an S5/S8a interface to exchange user plane data viaa protocol stack comprising an L1 layer, an L2 layer, the UDP/IP layer852, and the GTP-U 853. As discussed previously, NAS protocols maysupport the mobility of the UE 101 and the session management proceduresto establish and maintain IP connectivity between the UE 101 and theP-GW 223.

Moreover, although not shown by FIG. 8, an application layer may bepresent above the AP 863 and/or the transport network layer 854. Theapplication layer may be a layer in which a user of the UE 101, RAN node111, or other network element interacts with software applications beingexecuted, for example, by application circuitry 405 or applicationcircuitry 505, respectively. The application layer may also provide oneor more interfaces for software applications to interact withcommunications systems of the UE 101 or RAN node 111, such as thebaseband circuitry 710. In some implementations the IP layer and/or theapplication layer may provide the same or similar functionality aslayers 5-7, or portions thereof, of the Open Systems Interconnection(OSI) model (e.g., OSI Layer 7—the application layer, OSI Layer 6—thepresentation layer, and OSI Layer 5—the session layer).

FIGS. 9-11 show example procedures 900-1100, respectively, in accordancewith various embodiments. For illustrative purposes, the variousoperations of processes 900-1100 is described as being performed by UEs101 of FIG. 1 or elements thereof (e.g., components discussed withregard to platform 500 of FIG. 5), or a RAN node 111 of FIG. 1 orelements thereof (e.g., components discussed with regard toinfrastructure equipment 400 of FIG. 4). Additionally, the variousmessages/signaling communicated between the UE 101 and RAN node 111 maybe sent/received over the various interfaces discussed herein withrespect to FIGS. 1-8, and using the various mechanisms discussed hereinincluding those discussed herein with respect to FIGS. 1-8. Whileparticular examples and orders of operations are illustrated FIGS. 9-11,the depicted orders of operations should not be construed to limit thescope of the embodiments in any way. Rather, the depicted operations maybe re-ordered, broken into additional operations, combined, and/oromitted altogether while remaining within the spirit and scope of thepresent disclosure.

FIG. 9 depicts an example time domain table configuration process 900and an allocation table building process 912 according to variousembodiments. Processes 900 and 912 may be performed by the UE 101.Process 900 begins at operation 903 where the UE 101 receives an RRCmessage that includes a PDSCH and/or PUSCH configuration, such as thosediscussed previously with regard to tables 18-29. At operation 906, theUE 101 determines whether the configuration included in the RRC messageincludes a time domain resource allocation (TDRA) list, for example, thePDSCH-TimeDomainResourceAllocationList IE or thePUSCH-TimeDomainResourceAllocationList IE discussed previously withregard to tables 26-29.

If at operation 906 the UE 101 determines that the configuration doesnot include a TDRA list, then the UE 101 proceeds to operation 909 togenerate or otherwise use a default allocation table. For example, whenthe PDSCH-TimeDomainResourceAllocationList IE is not included in theconfiguration, the UE 101 may use one of default PDSCH time domainallocation A, B, C according to tables 3-5, respectively. As shown bytable 3, the particular default PDSCH time domain allocation to be usedmay be based on, inter alia, type of RNTI included or otherwiseassociated with the PDSCH, the PDCCH search space, the SS/PDCH block andCORESET multiplexing pattern, and/or some other suitable parameters. Inanother example, when the PUSCH-TimeDomainResourceAllocationList IE isnot included in the configuration, the UE 101 may use one of defaultPUSCH time domain allocation A according to table 10 or 10. As shown bytable 9, the particular default PUSCH time domain allocation to be usedmay be based on, inter alia, type of RNTI included or otherwiseassociated with the PUSCH, the PDCCH search space, and/or some othersuitable parameters.

If at operation 906 the UE 101 determines that the configuration doesinclude a TDRA list, then the UE 101 proceeds to perform the allocationtable building process 912 discussed infra. Process 900 ends afterperformance of operation 909 or the allocation table building process912.

Referring now to the allocation table building process 912 (on the rightside of FIG. 9). Process 912 begins at operation 915 where the UE 101identifies the TDRA list in the configuration included in the RRCmessage, and then proceeds to open loop operation 918 to process eachTDRA included in the TDRA list (e.g., eachPDSCH-TimeDomainResourceAllocation IE in thePDSCH-TimeDomainResourceAllocationList IE or eachPUSCH-TimeDomainResourceAllocation IE in thePUSCH-TimeDomainResourceAllocationList IE) in turn.

At operation 921, the UE 101 determines the TDRA parameters included inthe TDRA. The TDRA parameters include, inter alia, a slot offset (e.g.,K₀ for PDSCH or K₂ for PUSCH), the SLIV, and the mapping type. Atoperation 924, the UE 101 adds the TDRA to a corresponding record (orrow) in a TDRA table where each TDRA parameter is associated to arespective TDRA field (or column) in the TDRA table. The structure ofthe TDRA table may be similar to the default allocation tables 3-5and/or 9-10 discussed previously. In some embodiments, the UE 101 maydecode the SLIV to obtain a starting symbol (S) and an allocation length(L), which may then be placed into respective fields (or columns) in theTDRA table. At close loop operation 927, the UE 101 returns back to openloop operation 921 to process a next TDRA in the TDRA list, if any. Inaddition to adding the TDRA parameters to respective records (or rows),the UE 101 may also add a row index to each record (or row) thatcorresponds to the order in which the TDRA is processed, for example,the first TDRA to be processed may have a row index of 1, a second TDRAto be processed would have a row index of 2, and so forth. If there areno more TDRAs in the TDRA list, then the UE 101 returns back to process900.

FIG. 10 shows an example physical shared channel slot determinationprocess 1000 according to various embodiments. Process 1000 may beperformed by the UE 101 to determine a slot, slot starting symbol, andallocation length in which to receive a PDSCH or in which to transmit aPUSCH. Process 1000 begins at operation 1003 where the UE 101 receives aDCI that schedules transmission (Tx) or reception (Rx) of a physicalshared channel (e.g., a Rx of a PDSCH or Tx of a PUSCH). At operation1006 the UE 101 identifies an index row in the DCI, which may be, forexample, a value of a time domain allocation field of the DCI. Atoperation 1009, the UE 101 identifies a row of the allocation table(e.g., the table build or identified according to process 900 of FIG. 9)that corresponds to the index row. At operation 1012, the UE 101identifies TDRA parameters of the identified row, which may include forexample, a slot offset, starting symbol (S), allocation length (L), andmapping type.

At operation 1015, the UE 101 determines whether the identified startingsymbol (S) and allocation length (L) is a valid combination. Thevalidity of the S and L combination may be based on the type of physicalshared channel that is scheduled and the mapping type. As examples, thevalid S and L combinations for PDSCH are shown by table 1 supra and thevalid S and L combinations for PUSCH are shown by table 7 supra. If atoperation 1015 the UE 101 determines that the S and L combination is nota valid combination, then the UE 101 proceeds to operation 1024 todiscard the allocation or otherwise not Tx or Rx the physical sharedchannel. If at operation 1015 the UE 101 determines that the S and Lcombination is a valid combination, then the UE 101 proceeds tooperation 1018 to determine a slot, a starting symbol with respect to astart of the slot, and an allocation length. At operation 1021, the UE101 controls Rx or Tx of physical shared channel in the time domainallocation determined at operation 1018. Process 1000 ends afterperformance of operation 1021 or operation 1024.

FIG. 11 depicts an example time domain allocation configuration process1100 according to various embodiments. Process 1100 may be performed bya RAN node 111 to configure the UE 101 with an appropriate time domainallocation table, and to schedule Tx or Rx of a physical shared channelsuch as the PDSCH or PUSCH. Process 1100 begins at operation 1103 wherethe RAN node 111 generate an RRC message to at least include aconfiguration to indicate an allocation table to be used for determiningtime domain resource allocations for transmitting PUSCHs or receivingPDSCHs. For example, the configuration could the PDSCH-Config IE orPDSCH-ConfigCommon IE for configuring an appropriate PDSCH timeallocation table using the PDSCH-TimeDomainResourceAllocationList IE,and/or the configuration could the PUSCH-Config IE or PUSCH-ConfigCommonIE for configuring an appropriate PUSCH time allocation table using thePUSCH-TimeDomainResourceAllocationList IE. In another example, thePDSCH-Config IE or PDSCH-ConfigCommon IE may not include thePDSCH-TimeDomainResourceAllocationList IE to indicate that a defaultPDSCH time allocation table should be used, and/or the PUSCH-Config IEor PUSCH-ConfigCommon IE may not include thePUSCH-TimeDomainResourceAllocationList IE to indicate that a defaultPUSCH time allocation table should be used. At operation 1106, the RANnode 111 transmits the RRC message to the UE 101, and the UE 101 createsor uses the PDSCH and/or PUSCH tables as discussed previously withrespect to FIG. 9.

At operation 1109, the RAN node 111 generates a DCI to at least includea time domain resource assignment field to indicate a row index of theallocation table configured at operations 1103-1106. At operation 1112,the RAN node 111 transmits the DCI to the UE 101, which is then decodedby the UE 101. The UE 101 determines the slot, starting symbol, andallocation length in which to Tx or Rx the PUSCH or PDSCH as discussedpreviously with respect to FIG. 10. Process 1100 ends after performanceof operation 1112.

Some non-limiting examples are as follows. The following examplespertain to further embodiments, and specifics in the examples may beused anywhere in one or more embodiments discussed previously. Any ofthe following examples may be combined with any other example or anyembodiment discussed herein.

Example 1 includes an integrated circuit (IC) to be implemented in auser equipment (UE), the IC arranged to: determine, based on a timedomain resource field of downlink control information (DCI), a startingsymbol relative to a start of a slot in which a physical downlink sharedchannel (PDSCH) scheduled by the DCI is to be received and an allocationlength, wherein the allocation length is a number of consecutive symbolscounting from the starting symbol, and wherein a combination of thestarting symbol and the allocation length is based on a PDSCH mappingtype to be assumed for reception of the PDSCH; and control receipt ofthe PDSCH based on the starting symbol and the allocation length.

Example 2 includes the IC of example 1 and/or some other examplesherein, wherein the time domain resource field indicates a row index,and the IC is arranged to: identify, in a row corresponding to the rowindex, a slot offset, the PDSCH mapping type, a slot offset, and a startand length indicator (SLIV), wherein the SLIV is to indicate thestarting symbol and the allocation length.

Example 3 includes the IC of example 2 and/or some other examplesherein, wherein the PDSCH mapping type is either a mapping type A or amapping type B.

Example 4 includes the IC of example 3 and/or some other examplesherein, wherein, when the PDSCH mapping type is the mapping type A, theallocation length is any number from three to fourteen, and the startingsymbol is one of zero, one, two, or three.

Example 5 includes the IC of examples 3-4 and/or some other examplesherein, wherein, when the PDSCH mapping type is the mapping type B, theallocation length is either two, four, or seven symbols, and thestarting symbol is any number from zero to twelve.

Example 6 includes the IC of examples 3-5 and/or some other examplesherein, wherein the combination of the starting symbol and theallocation length is any number from three to fourteen when the PDSCHmapping type is the mapping type A, and the combination of the startingsymbol and the allocation length is any number from two to fourteen whenthe PDSCH mapping type is the mapping type B.

Example 7 includes the IC of examples 2-6 and/or some other examplesherein, wherein the IC is arranged to: determine the allocation length(L) and the starting symbol (S) from the SLIV, wherein if (L−1)≤7, thenSLIV=14·(L−1)+S, and if (L−1)>7, then SLIV=14·(14−L+1)+(14−1−S), wherein0<L≤14−S.

Example 8 includes the IC of examples 2-7 and/or some other examplesherein, wherein the IC is arranged to: identify, based on a receivedRadio Resource Control (RRC) message, a time domain allocation listinformation element (IE) comprising one or more time domain allocationIEs, wherein each time domain allocation IE of the one or more timedomain allocation IEs includes a slot offset field, a SLIV field, and amapping type field; and generate a time domain resource allocation tableto include one or more rows corresponding to the one or more time domainallocation IEs such that each row of the one or more rows includes acorresponding slot offset field, mapping type field, a starting symbolfield and an allocation length field, wherein the starting symbol andthe allocation length fields of each row are based on the SLIV field ofa respective time domain allocation IE.

Example 9 includes the IC of example 1 and/or some other examplesherein, wherein the PDSCH is a first PDSCH, the slot is a first slot,the starting symbol is a first starting symbol, and the allocationlength is a first allocation length, and the IC is arranged to:determine, based on another time domain resource field of another DCI, asecond starting symbol relative to a start of a second slot in whichanother PDSCH scheduled by the other DCI is to be received and a secondallocation length, wherein the second allocation length has a samenumber of consecutive symbols as the first allocation length, andwherein the second slot is a next consecutive slot in time after thefirst slot without a gap therebetween.

Example 10 includes the IC of example 1 and/or some other examplesherein, wherein the IC is arranged to: determine the combination of thestarting symbol and the allocation length such that the combination ofthe starting symbol and the allocation length does not cross a slotboundary of the slot.

Example 11 includes an integrated circuit (IC) to be implemented in auser equipment (UE), the IC arranged to: determine, based on a timedomain resource field of downlink control information (DCI), a startingsymbol relative to a start of a slot in which a physical uplink sharedchannel (PUSCH) scheduled by the DCI is to be transmitted and anallocation length, wherein the allocation length is a number ofconsecutive symbols counting from the starting symbol, and wherein acombination of the starting symbol and the allocation length is based ona PUSCH mapping type to be assumed for the transmission of the PUSCH;and control transmission of the PUSCH based on the starting symbol andthe allocation length.

Example 12 includes the IC of example 11 and/or some other examplesherein, wherein the time domain resource field indicates a row index,and the IC is arranged to: identify, in a row corresponding to theidentified row index, a slot offset, the PUSCH mapping type, a slotoffset, and a start and length indicator (SLIV), wherein the SLIV is toindicate the starting symbol and the allocation length.

Example 13 includes the IC of example 12 and/or some other examplesherein, wherein the PUSCH mapping type is either a mapping type A or amapping type B.

Example 14 includes the IC of example 13, wherein, when the PUSCHmapping type is the mapping type A, the allocation length is any numberfrom four to fourteen, and the starting symbol is zero.

Example 15 includes the IC of examples 13-14 and/or some other examplesherein, wherein, when the PUSCH mapping type is the mapping type B, theallocation length is any number from one to fourteen, and the startingsymbol is any number from zero to thirteen.

Example 16 includes the IC of examples 13-15 and/or some other examplesherein, wherein the combination of the starting symbol and theallocation length is any number from three to fourteen when the PUSCHmapping type is the mapping type A, and the combination of the startingsymbol and the allocation length is any number from two to fourteen whenthe PUSCH mapping type is the mapping type B.

Example 17 includes the IC of example 12 and/or some other examplesherein, wherein the IC is arranged to: determine the allocation length(L) and the starting symbol (S) from the SLIV, wherein if (L−1)≤7, thenSLIV=14·(L−1)+S, and if (L−1)>7, then SLIV=14·(14−L+1)+(14−1−S), wherein0<L≤14−S.

Example 18 includes the IC of examples 12-17 and/or some other examplesherein, wherein the IC is arranged to: identify, based on a receivedRadio Resource Control (RRC) message, a time domain allocation listinformation element (IE) comprising one or more time domain allocationIEs, wherein each time domain allocation IE of the one or more timedomain allocation IEs includes a slot offset field, a SLIV field, and amapping type field; and generate a time domain resource allocation tableto include one or more rows corresponding to the one or more time domainallocation IEs such that each row of the one or more rows includes acorresponding slot offset field, mapping type field, a starting symbolfield and an allocation length field, wherein the starting symbol andthe allocation length fields of each row are based on the SLIV field ofa respective time domain allocation IE.

Example 19 includes the IC of examples 11-18 and/or some other examplesherein, wherein the PDSCH is a first PUSCH, the slot is a first slot,the starting symbol is a first starting symbol, and the allocationlength is a first allocation length, and wherein the IC is arranged to:determine, based on another time domain resource field of another DCI, asecond starting symbol relative to a start of a second slot in whichanother PUSCH scheduled by the other DCI is to be received and a secondallocation length, wherein the second allocation length has a samenumber of consecutive symbols as the first allocation length, andwherein the second slot is a next consecutive slot in time after thefirst slot without a gap therebetween.

Example 20 includes the IC of examples 11-19 and/or some other examplesherein, wherein the IC is arranged to: determine the combination of thestarting symbol and the allocation length such that the combination ofthe starting symbol and the allocation length does not cross a slotboundary of the slot.

Example 21 includes the IC of any of examples 1-20 and/or some otherexamples herein, wherein the UE supports up to eight layers for downlinktransmission, wherein a maximum number of layers supported by the UE fora serving cell is a maximum number of layers for one transport block(TB).

Example 22 includes the IC of any of example 21 and/or some otherexamples herein, wherein the maximum number of layers supported by theUE for the serving cell for a TB such that limited buffer rate matching(LBRM) is applied based on four layers.

Example 23 includes the IC of any of examples 21-22 and/or some otherexamples herein, wherein the IC is arranged to: select one or more bitsfor a low density parity check (LDPC) rate matching procedure based onthe maximum number of layers for one TB supported by the UE.

Example 24 includes the IC of any of examples 1-23 and/or some otherexamples herein, wherein the IC is a System-on-Chip (SoC),System-in-Package (SiP), or a Multi-Chip Package (MCP), and wherein theIC includes processor circuitry coupled with memory circuitry.

Example 25 includes an apparatus to be implemented in a Next GenerationRadio Access Network (NG-RAN) node, the apparatus comprising: processorcircuitry arranged to generate downlink control information (DCI) to atleast include a time domain resource assignment field, wherein the timedomain resource assignment field is to include a value to indicate a rowindex of an allocation table, and wherein a row in the allocation tablecorresponding to the row index at least defines a slot offset, a mappingtype, and a start and length indicator (SLIV) or directly a start symboland an allocation length; and interface circuitry coupled with theprocessor circuitry, the interface circuitry arranged to provide the DCIto a radio front end module (RFEM) for transmission to a user equipment(UE).

Example 26 includes the apparatus of example 25 and/or some otherexamples herein, wherein the DCI is to schedule a Physical DownlinkShared Channel (PDSCH), the mapping type is a PDSCH mapping type to beassumed for reception of the PDSCH, the PDSCH mapping type is either aPDSCH mapping type A or a PDSCH mapping type B, and wherein: when thePDSCH mapping type is the mapping type A, the allocation length is anynumber from three to fourteen, and the starting symbol is one of zero,one, two, or three; and when the PDSCH mapping type is the mapping typeB, the allocation length is either two, four, or seven symbols, and thestarting symbol is any number from zero to twelve.

Example 27 includes the apparatus of example 25 and/or some otherexamples herein, wherein the DCI is to schedule a Physical Uplink SharedChannel (PUSCH), the mapping type is a PUSCH mapping type to be assumedfor transmission of the PUSCH, the PUSCH mapping type is either a PUSCHmapping type A or a PUSCH mapping type B, and wherein: when the PUSCHmapping type is the mapping type A, the allocation length is any numberfrom four to fourteen, and the starting symbol is zero; and when thePUSCH mapping type is the mapping type B, the allocation length is anynumber from one to fourteen, and the starting symbol is any number fromzero to thirteen.

Example 28 includes the apparatus of examples 25-27 and/or some otherexamples herein, wherein: the processor circuitry is arranged togenerate a Radio Resource Control (RRC) message to include aconfiguration, wherein the configuration is to include a time domainallocation list (TimeDomainAllocationList) information element (IE),wherein the TimeDomainAllocationList IE includes one or more time domainallocation (TimeDomainAllocation) IEs, wherein each TimeDomainAllocationIE of the one or more TimeDomainAllocation IEs is to correspond to a rowin the allocation table; and the interface circuitry arranged to providethe RRC message to the RFEM for transmission to the UE prior totransmission of the DCI.

Example 29 includes the apparatus of examples 25-28 and/or some otherexamples herein, wherein: the processor circuitry is arranged togenerate an RRC message to include a configuration, wherein theconfiguration is to not include a TimeDomainAllocationList IE toindicate to use a default allocation table based on a type of RadioNetwork Temporary Identifier (RNTI) to be included with a transmissionscheduled by the DCI; and the interface circuitry arranged to providethe RRC message to the RFEM for transmission to the UE prior totransmission of the DCI.

Example 30 includes the apparatus of any of examples 25-29 and/or someother examples herein, wherein the apparatus is a System-on-Chip (SoC),System-in-Package (SiP), or a Multi-Chip Package (MCP).

Example 31 includes a method comprising: determining or causing todetermine, based on a time domain resource field of downlink controlinformation (DCI), a starting symbol relative to a start of a slot inwhich a physical downlink shared channel (PDSCH) scheduled by the DCI isto be received and an allocation length, wherein the allocation lengthis a number of consecutive symbols counting from the starting symbol,and wherein a combination of the starting symbol and the allocationlength is based on a PDSCH mapping type to be assumed for reception ofthe PDSCH; and controlling receipt of the PDSCH based on the startingsymbol and the allocation length.

Example 32 includes the method of example 31 and/or some other examplesherein, wherein the time domain resource field indicates a row index,and the method comprises: identifying or causing to identify, in a rowcorresponding to the row index, a slot offset, the PDSCH mapping type, aslot offset, and a start and length indicator (SLIV), wherein the SLIVis to indicate the starting symbol and the allocation length.

Example 33 includes the method of example 32 and/or some other examplesherein, wherein the PDSCH mapping type is either a mapping type A or amapping type B.

Example 34 includes the method of example 33 and/or some other examplesherein, wherein, when the PDSCH mapping type is the mapping type A, theallocation length is any number from three to fourteen, and the startingsymbol is one of zero, one, two, or three.

Example 35 includes the method of examples 33-34 and/or some otherexamples herein, wherein, when the PDSCH mapping type is the mappingtype B, the allocation length is either two, four, or seven symbols, andthe starting symbol is any number from zero to twelve.

Example 36 includes the method of examples 33-35 and/or some otherexamples herein, wherein the combination of the starting symbol and theallocation length is any number from three to fourteen when the PDSCHmapping type is the mapping type A, and the combination of the startingsymbol and the allocation length is any number from two to fourteen whenthe PDSCH mapping type is the mapping type B.

Example 37 includes the method of examples 32-36 and/or some otherexamples herein, wherein the method comprises: determining or causing todetermine the allocation length (L) and the starting symbol (S) from theSLIV, wherein: if (L−1)≤7, then SLIV=14·(L−1)+S, and if (L−1)>7, thenSLIV=14·(14−L+1)+(14−1−S), wherein 0<L≤14−S.

Example 38 includes the method of examples 32-37 and/or some otherexamples herein, wherein the method comprises: identifying or causing toidentify, based on a received Radio Resource Control (RRC) message, atime domain allocation list information element (IE) comprising one ormore time domain allocation IEs, wherein each time domain allocation IEof the one or more time domain allocation IEs includes a slot offsetfield, a SLIV field, and a mapping type field; and generating or causingto generate a time domain resource allocation table to include one ormore rows corresponding to the one or more time domain allocation IEssuch that each row of the one or more rows includes a corresponding slotoffset field, mapping type field, a starting symbol field and anallocation length field, wherein the starting symbol and the allocationlength fields of each row are based on the SLIV field of a respectivetime domain allocation IE.

Example 39 includes the method of example 31 and/or some other examplesherein, wherein the PDSCH is a first PDSCH, the slot is a first slot,the starting symbol is a first starting symbol, and the allocationlength is a first allocation length, and the method comprising:determining or causing to determine, based on another time domainresource field of another DCI, a second starting symbol relative to astart of a second slot in which another PDSCH scheduled by the other DCIis to be received and a second allocation length, wherein the secondallocation length has a same number of consecutive symbols as the firstallocation length, and wherein the second slot is a next consecutiveslot in time after the first slot without a gap therebetween.

Example 40 includes the method of example 31 and/or some other examplesherein, wherein the method comprises: determining or causing todetermine the combination of the starting symbol and the allocationlength such that the combination of the starting symbol and theallocation length does not cross a slot boundary of the slot.

Example 41 includes a method comprising: determining or causing todetermine, based on a time domain resource field of downlink controlinformation (DCI), a starting symbol relative to a start of a slot inwhich a physical uplink shared channel (PUSCH) scheduled by the DCI isto be transmitted and an allocation length, wherein the allocationlength is a number of consecutive symbols counting from the startingsymbol, and wherein a combination of the starting symbol and theallocation length is based on a PUSCH mapping type to be assumed for thetransmission of the PUSCH; and controlling transmission of the PUSCHbased on the starting symbol and the allocation length.

Example 42 includes the method of example 41 and/or some other examplesherein, wherein the time domain resource field indicates a row index,and the method comprises: identifying or causing to identify, in a rowcorresponding to the identified row index, a slot offset, the PUSCHmapping type, a slot offset, and a start and length indicator (SLIV),wherein the SLIV is to indicate the starting symbol and the allocationlength.

Example 43 includes the method of example 42 and/or some other examplesherein, wherein the PUSCH mapping type is either a mapping type A or amapping type B.

Example 44 includes the method of example 43, wherein, when the PUSCHmapping type is the mapping type A, the allocation length is any numberfrom four to fourteen, and the starting symbol is zero.

Example 45 includes the method of examples 43-44 and/or some otherexamples herein, wherein, when the PUSCH mapping type is the mappingtype B, the allocation length is any number from one to fourteen, andthe starting symbol is any number from zero to thirteen.

Example 46 includes the method of examples 43-45 and/or some otherexamples herein, wherein the combination of the starting symbol and theallocation length is any number from three to fourteen when the PUSCHmapping type is the mapping type A, and the combination of the startingsymbol and the allocation length is any number from two to fourteen whenthe PUSCH mapping type is the mapping type B.

Example 47 includes the method of example 42 and/or some other examplesherein, wherein the method comprises: determining or causing todetermine the allocation length (L) and the starting symbol (S) from theSLIV, wherein: if (L−1)≤7, then SLIV=14·(L−1)+S, and if (L−1)>7, thenSLIV=14·(14−L+1)+(14−1−S), wherein 0<L≤14−S.

Example 48 includes the method of examples 42-47 and/or some otherexamples herein, wherein the method comprises: identifying or causing toidentify, based on a received Radio Resource Control (RRC) message, atime domain allocation list information element (IE) comprising one ormore time domain allocation IEs, wherein each time domain allocation IEof the one or more time domain allocation IEs includes a slot offsetfield, a SLIV field, and a mapping type field; and generating or causingto generate a time domain resource allocation table to include one ormore rows corresponding to the one or more time domain allocation IEssuch that each row of the one or more rows includes a corresponding slotoffset field, mapping type field, a starting symbol field and anallocation length field, wherein the starting symbol and the allocationlength fields of each row are based on the SLIV field of a respectivetime domain allocation IE.

Example 49 includes the method of examples 41-48 and/or some otherexamples herein, wherein the PDSCH is a first PUSCH, the slot is a firstslot, the starting symbol is a first starting symbol, and the allocationlength is a first allocation length, and wherein the method comprises:determining or causing to determine, based on another time domainresource field of another DCI, a second starting symbol relative to astart of a second slot in which another PUSCH scheduled by the other DCIis to be received and a second allocation length, wherein the secondallocation length has a same number of consecutive symbols as the firstallocation length, and wherein the second slot is a next consecutiveslot in time after the first slot without a gap therebetween.

Example 50 includes the method of examples 41-49 and/or some otherexamples herein, wherein the method comprises: determining or causing todetermine the combination of the starting symbol and the allocationlength such that the combination of the starting symbol and theallocation length does not cross a slot boundary of the slot.

Example 51 includes the method of any of examples 31-50 and/or someother examples herein, wherein the UE supports up to eight layers fordownlink transmission, wherein a maximum number of layers supported bythe UE for a serving cell is a maximum number of layers for onetransport block (TB).

Example 52 includes the method of any of example 51 and/or some otherexamples herein, wherein the maximum number of layers supported by theUE for the serving cell for a TB such that limited buffer rate matching(LBRM) is applied based on four layers.

Example 53 includes the method of any of examples 51-52 and/or someother examples herein, wherein the method comprises: selecting orcausing to select one or more bits for a low density parity check (LDPC)rate matching procedure based on the maximum number of layers for one TBsupported by the UE.

Example 54 includes the method of any of examples 31-53 and/or someother examples herein, wherein the method is to be performed by aSystem-on-Chip (SoC), System-in-Package (SiP), or a Multi-Chip Package(MCP) implemented in a user equipment (UE).

Example 55 includes a method comprising: generating or causing togenerate downlink control information (DCI) to at least include a timedomain resource assignment field, wherein the time domain resourceassignment field is to include a value to indicate a row index of anallocation table, and wherein a row in the allocation tablecorresponding to the row index at least defines a slot offset, a mappingtype, and a start and length indicator (SLIV) or directly a start symboland an allocation length; and controlling transmission of the DCI to auser equipment (UE).

Example 56 includes the method of example 55 and/or some other examplesherein, wherein the DCI is to schedule a Physical Downlink SharedChannel (PDSCH), the mapping type is a PDSCH mapping type to be assumedfor reception of the PDSCH, the PDSCH mapping type is either a PDSCHmapping type A or a PDSCH mapping type B, and wherein: when the PDSCHmapping type is the mapping type A, the allocation length is any numberfrom three to fourteen, and the starting symbol is one of zero, one,two, or three; and when the PDSCH mapping type is the mapping type B,the allocation length is either two, four, or seven symbols, and thestarting symbol is any number from zero to twelve.

Example 57 includes the method of example 55 and/or some other examplesherein, wherein the DCI is to schedule a Physical Uplink Shared Channel(PUSCH), the mapping type is a PUSCH mapping type to be assumed fortransmission of the PUSCH, the PUSCH mapping type is either a PUSCHmapping type A or a PUSCH mapping type B, and wherein: when the PUSCHmapping type is the mapping type A, the allocation length is any numberfrom four to fourteen, and the starting symbol is zero; and when thePUSCH mapping type is the mapping type B, the allocation length is anynumber from one to fourteen, and the starting symbol is any number fromzero to thirteen.

Example 58 includes the method of examples 55-57 and/or some otherexamples herein, wherein the method comprises:

generating or causing to generate a Radio Resource Control (RRC) messageto include a configuration, wherein the configuration is to include atime domain allocation list (TimeDomainAllocationList) informationelement (IE), wherein the TimeDomainAllocationList IE includes one ormore time domain allocation (TimeDomainAllocation) IEs, wherein eachTimeDomainAllocation IE of the one or more TimeDomainAllocation IEs isto correspond to a row in the allocation table; and controllingtransmission of the RRC message to the UE prior to transmission of theDCI.

Example 59 includes the method of examples 55-58 and/or some otherexamples herein, wherein the method comprises: generating or causing togenerate an RRC message to include a configuration, wherein theconfiguration is to not include a TimeDomainAllocationList IE toindicate to use a default allocation table based on a type of RadioNetwork Temporary Identifier (RNTI) to be included with a transmissionscheduled by the DCI; and controlling transmission of the RRC message tothe RFEM for transmission to the UE prior to transmission of the DCI.

Example 60 includes the method of any of examples 55-59 and/or someother examples herein, wherein the method is to be performed by aSystem-on-Chip (SoC), System-in-Package (SiP), or a Multi-Chip Package(MCP) implemented in a Next Generation Radio Access Network (NG-RAN)node.

Example 61 may include an apparatus comprising means to perform one ormore elements of a method described in or related to any of examples1-60, or any other method or process described herein.

Example 62 may include one or more non-transitory computer-readablemedia comprising instructions to cause an electronic device, uponexecution of the instructions by one or more processors of theelectronic device, to perform one or more elements of a method describedin or related to any of examples 1-60, or any other method or processdescribed herein.

Example 63 may include an apparatus comprising logic, modules, orcircuitry to perform one or more elements of a method described in orrelated to any of examples 1-60, or any other method or processdescribed herein.

Example 64 may include a method, technique, or process as described inor related to any of examples 1-60, or portions or parts thereof.

Example 65 may include an apparatus comprising: one or more processorsand one or more computer-readable media comprising instructions that,when executed by the one or more processors, cause the one or moreprocessors to perform the method, techniques, or process as described inor related to any of examples 1-60, or portions thereof.

Example 66 may include a signal as described in or related to any ofexamples 1-60, or portions or parts thereof.

Example 67 includes a packet, frame, segment, protocol data unit (PDU),or message as described in or related to any of examples 1-60, orportions or parts thereof, or otherwise described in the presentdisclosure

Example 68 may include a signal in a wireless network as shown anddescribed herein. Example 69 may include a method of communicating in awireless network as shown and described herein. Example 70 may include asystem for providing wireless communication as shown and describedherein. Example 71 may include a device for providing wirelesscommunication as shown and described herein. Any of the above-describedexamples may be combined with any other example (or combination ofexamples), unless explicitly stated otherwise. The foregoing descriptionof one or more implementations provides illustration and description,but is not intended to be exhaustive or to limit the scope ofembodiments to the precise form disclosed. Modifications and variationsare possible in light of the above teachings or may be acquired frompractice of various embodiments.

The present disclosure has been described with reference to flowchartillustrations and/or block diagrams of methods, apparatus (systems),and/or computer program products according to embodiments of the presentdisclosure. In the drawings, some structural or method features may beshown in specific arrangements and/or orderings. However, it should beappreciated that such specific arrangements and/or orderings may not berequired. Rather, in some embodiments, such features may be arranged ina different manner and/or order than shown in the illustrative figures.Additionally, the inclusion of a structural or method feature in aparticular figure is not meant to imply that such feature is required inall embodiments and, in some embodiments, may not be included or may becombined with other features.

The flowchart and block diagrams in the figures illustrate thearchitecture, functionality, and operation of possible implementationsof systems, methods and computer program products according to variousembodiments of the present disclosure. In this regard, each block in theflowchart or block diagrams may represent a module, segment, or portionof code, which comprises one or more executable instructions forimplementing the specified logical function(s). It should also be notedthat, in some alternative implementations, the functions noted in theblock may occur out of the order noted in the figures. For example, twoblocks shown in succession may, in fact, be executed substantiallyconcurrently, or the blocks may sometimes be executed in the reverseorder, depending upon the functionality involved. It will also be notedthat each block of the block diagrams and/or flowchart illustration, andcombinations of blocks in the block diagrams and/or flowchartillustration, can be implemented by special purpose hardware-basedsystems that perform the specified functions or acts, or combinations ofspecial purpose hardware and computer instructions.

The terminology used herein is for the purpose of describing particularembodiments only and is not intended to be limiting of the disclosure.As used herein, the singular forms “a,” “an” and “the” are intended toinclude plural forms as well, unless the context clearly indicatesotherwise. It will be further understood that the terms “comprises”and/or “comprising,” when used in this specification, specific thepresence of stated features, integers, steps, operations, elements,and/or components, but do not preclude the presence or addition of oneor more other features, integers, steps, operation, elements,components, and/or groups thereof.

For the purposes of the present disclosure, the phrase “A and/or B”means (A), (B), or (A and B). For the purposes of the presentdisclosure, the phrase “A, B, and/or C” means (A), (B), (C), (A and B),(A and C), (B and C), or (A, B and C). The description may use thephrases “in an embodiment,” or “In some embodiments,” which may eachrefer to one or more of the same or different embodiments. Furthermore,the terms “comprising,” “including,” “having,” and the like, as usedwith respect to embodiments of the present disclosure, are synonymous.

The terms “coupled,” “communicatively coupled,” along with derivativesthereof are used herein. The term “coupled” may mean two or moreelements are in direct physical or electrical contact with one another,may mean that two or more elements indirectly contact each other butstill cooperate or interact with each other, and/or may mean that one ormore other elements are coupled or connected between the elements thatare said to be coupled with each other. The term “directly coupled” maymean that two or more elements are in direct contact with one another.The term “communicatively coupled” may mean that two or more elementsmay be in contact with one another by a means of communication includingthrough a wire or other interconnect connection, through a wirelesscommunication channel or ink, and/or the like.

As used herein, the term “circuitry” refers to a circuit or system ofmultiple circuits configured to perform a particular function in anelectronic device. The circuit or system of circuits may be part of, orinclude one or more hardware components, such as a logic circuit, aprocessor (shared, dedicated, or group) and/or memory (shared,dedicated, or group), ASICs, FPDs (e.g., FPGAs, PLDs, CPLDs, HCPLDs, astructured ASICs, or a programmable SoCs, DSPs, etc., that areconfigured to provide the described functionality. In addition, the term“circuitry” may also refer to a combination of one or more hardwareelements with the program code used to carry out the functionality ofthat program code. Some types of circuitry may execute one or moresoftware or firmware programs to provide at least some of the describedfunctionality. Such a combination of hardware elements and program codemay be referred to as a particular type of circuitry.

As used herein, the term “processor circuitry” refers to, is part of, orincludes circuitry capable of sequentially and automatically carryingout a sequence of arithmetic or logical operations, or recording,storing, and/or transferring digital data. and/or any other devicecapable of executing or otherwise operating computer-executableinstructions, such as program code, software modules, and/or functionalprocesses.

As used herein, the term “module” refers to one or more independentelectronic circuits packaged onto a circuit board, SoC, SiP, etc.,configured to provide a basic function within a computer system.

As used herein, the term “module” refers to, be part of, or include anFPD, ASIC, a processor (shared, dedicated, or group) and/or memory(shared, dedicated, or group), etc., that execute one or more softwareor firmware programs, a combinational logic circuit, and/or othersuitable components that provide the described functionality.

As used herein, the term “interface circuitry” refers to, is part of, orincludes circuitry providing for the exchange of information between twoor more components or devices. The term “interface circuitry” refers toone or more hardware interfaces, for example, buses, input/output (I/O)interfaces, peripheral component interfaces, network interface cards,and/or the like.

As used herein, the term “device” refers to a physical entity embeddedinside, or attached to, another physical entity in its vicinity, withcapabilities to convey digital information from or to that physicalentity. As used herein, the term “element” refers to a unit that isindivisible at a given level of abstraction and has a clearly definedboundary, wherein an element may be any type of entity. As used herein,the term “controller” refers to an element or entity that has thecapability to affect a physical entity, such as by changing its state orcausing the physical entity to move. As used herein, the term “entity”refers to (1) a distinct component of an architecture or device, or (2)information transferred as a payload. The term “network element” as usedherein refers to physical or virtualized equipment and/or infrastructureused to provide wired or wireless communication network services. Theterm “network element” may be considered synonymous to and/or referredto as a networked computer, networking hardware, network equipment,network node, router, switch, hub, bridge, radio network controller, RANdevice, RAN node, gateway, server, virtualized VNF, NFVI, and/or thelike.

As used herein, the term “computer system” refers to any typeinterconnected electronic devices, computer devices, or componentsthereof. Additionally, the term “computer system” and/or “system” refersto various components of a computer that are communicatively coupledwith one another, or otherwise organized to accomplish one or morefunctions. Furthermore, the term “computer system” and/or “system”refers to multiple computer devices and/or multiple computing systemsthat are communicatively coupled with one another and configured toshare computing and/or networking resources.

As used herein, the term “architecture” refers to a fundamentalorganization of a system embodied in its components, their relationshipsto one another, and to an environment, as well as to the principlesguiding its design and evolution.

As used herein, the term “appliance,” “computer appliance,” or the like,refers to a discrete hardware device with integrated program code (e.g.,software or firmware) that is specifically or specially designed toprovide a specific computing resource. A “virtual appliance” is avirtual machine image to be implemented by a hypervisor-equipped devicethat virtualizes or emulates a computer appliance or otherwise isdedicated to provide a specific computing resource.

As used herein, the term “user equipment” or “UE” as used herein refersto a device with radio communication capabilities and may describe aremote user of network resources in a communications network. The term“user equipment” or “UE” may be considered synonymous to, and may bereferred to as, client, mobile, mobile device, mobile terminal, userterminal, mobile unit, mobile station, mobile user, subscriber, user,remote station, access agent, user agent, receiver, radio equipment,reconfigurable radio equipment, reconfigurable mobile device, etc.Furthermore, the term “user equipment” or “UE” may include any type ofwireless/wired device or any computing device including a wirelesscommunications interface.

As used herein, the term “channel” as used herein refers to anytransmission medium, either tangible or intangible, which is used tocommunicate data or a data stream. The term “channel” may be synonymouswith and/or equivalent to “communications channel,” “data communicationschannel,” “transmission channel,” “data transmission channel,” “accesschannel,” “data access channel,” “link,” “data link,” “carrier,”“radiofrequency carrier,” and/or any other like term denoting a pathwayor medium through which data is communicated. Additionally, the term“link” as used herein refers to a connection between two devices througha RAT for the purpose of transmitting and receiving information.

As used herein, the terms “instantiate,” “instantiation,” and the likerefers to the creation of an instance, and an “instance” refers to aconcrete occurrence of an object, which may occur, for example, duringexecution of program code.

As used herein, a “database object”, “data object”, or the like refersto any representation of information in a database that is in the formof an object, attribute-value pair (AVP), key-value pair (KVP), tuple,etc., and may include variables, data structures, functions, methods,classes, database records, database fields, database entities,associations between data and database entities (also referred to as a“relation”), and the like.

As used herein, the term “resource” refers to a physical or virtualdevice, a physical or virtual component within a computing environment,and/or a physical or virtual component within a particular device, suchas computer devices, mechanical devices, memory space, processor/CPUtime, processor/CPU usage, processor and accelerator loads, hardwaretime or usage, electrical power, input/output operations, ports ornetwork sockets, channel/link allocation, throughput, memory usage,storage, network, database and applications, workload units, and/or thelike. The term “network resource” refers to a resource hosted by aremote entity (e.g., a cloud computing service) and accessible over anetwork. The term “on-device resource” refers to a resource hostedinside a device and enabling access to the device, and thus, to therelated physical entity. System resources may be considered as a set ofcoherent functions, network data objects or services, accessible througha server where such system resources reside on a single host or multiplehosts and are clearly identifiable. Additionally, a “virtualizedresource” refers to compute, storage, and/or network resources providedby virtualization infrastructure to an application, such as amulti-access edge applications. The term “information element” refers toa structural element containing one or more fields. The term “field”refers to individual contents of an information element, or a dataelement that contains content.

For the purposes of the present document, the abbreviations listed intable 42 may apply to the examples and embodiments discussed herein.

TABLE 42 3GPP Third Generation Partnership Project 4G Fourth Generation5G Fifth Generation 5GC 5G Core network ACK Acknowledgement AFApplication Function AMF Access and Mobility Management Function ANAccess Network AP Application Protocol, Antenna Port, Access Point APIApplication Programming Interface ARQ Automatic Repeat Request AS AccessStratum ASN.1 Abstract Syntax Notation One AUSF Authentication ServerFunction BS Base Station BSR Buffer Status Report BW Bandwidth BWPBandwidth Part CA Carrier Aggregation, Certification Authority CCComponent Carrier, Country Code, Cryptographic Checksum CCA ClearChannel Assessment CCE Control Channel Element CCCH Common ControlChannel CDMA Code-Divisioni Multiple Access CI Cell Identity CID Cell-ID(e.g., positioning method) CM Connection Management, ConditionalMandatory CMAS Commercial Mobile Alert Service CORESET Control ResourceSet CP Control Plane, Cyclic Prefix, Connection Point CPICH Common PilotChannel CQI Channel Quality Indicator CPU CSI processing unit, CentralProcessing Unit CRAN Cloud Radio Access Network, Cloud RAN CRC CyclicRedundancy Check CRI Channel-State Information Resource Indicator,CSI-RS Resource Indicator C-RNTI Cell RNTI CS Circuit Switched CS-RNTIConfigured Scheduling RNTI CSAR Cloud Service Archive CSI Channel-StateInformation CSI-IM CSI Interference Measurement CSI-RS CSI ReferenceSignal CSI-RSRP CSI reference signal received power CSI-RSRQ CSIreference signal received quality CSI-SINR CSI signal-to-noise andinterference ratio CSMA Carrier Sense Multiple Access CSMA/CA CSMA withcollision avoidance CSS Common Search Space, Cell-specific Search SpaceCTS Clear-to-Send D2D Device-to-Device DC Dual Connectivity, DirectCurrent DCI Downlink Control Information DL Downlink DL-SCH DownlinkShared Channel DM-RS, DMRS Demodulation Reference Signal DN Data networkDRB Data Radio Bearer DRS Discovery Reference Signal DRX DiscontinuousReception ECCA extended clear channel assessment, extended CCA ECCEEnhanced Control Channel Element, Enhanced CCE ED Energy Detection EDGEEnhanced Datarates for GSM Evolution (GSM Evolution) EGMF ExposureGovernance Management Function EGPRS Enhanced GPRS eLAA enhanced LAA EMElement Manager eNB evolved NodeB, E-UTRAN Node B EPC Evolved PacketCore EPDCCH enhanced PDCCH, enhanced Physical Downlink Control CannelEPS Evolved Packet System EREG enhanced REG, enhanced resource elementgroups E-UTRA Evolved UTRA E-UTRAN Evolved UTRAN F1AP F1 ApplicationProtocol F1-C F1 Control plane interface F1-U F1 User plane interfaceFDD Frequency Division Duplex FDM Frequency Division Multiplex FDMAFrequency Division Multiple Access FFS For Further Study FFT FastFourier Transformation feLAA further enhanced Licensed Assisted Access,further enhanced LAA FN Frame Number FPGA Field-Programmable Gate ArrayFR Frequency Range G-RNTI GERAN Radio Network Temporary Identity GERANGSM EDGE RAN GGSN Gateway GPRS Support Node GLONASS GLObal'nayaNAvigatsionnaya Sputnikovaya Sistema (Engl.: Global Navigation SatelliteSystem) gNB Next Generation NodeB gNB-CU gNB-centralized unit, NextGeneration NodeB centralized unit gNB-DU gNB-distributed unit, NextGeneration NodeB distributed unit GNSS Global Navigation SatelliteSystem GPRS General Packet Radio Service GSM Global System for MobileCommunications, Groupe Special Mobile GTP GPRS Tunnelling Protocol GTP-UGPRS Tunnelling Protocol for User Plane GUMMEI Globally Unique MMEIdentifier GUTI Globally Unique Temporary UE Identity HARQ Hybrid ARQ,Hybrid Automatic Repeat Request HANDO, HO Handover HFN HyperFrame NumberHLR Home Location Register HPLMN Home PLMN HSS Home Subscriber ServerHTTP Hyper Text Transfer Protocol HTTPS Hyper Text Transfer ProtocolSecure (https is http/1.1 over SSL, i.e. port 443) ID Identity,identifier IDFT Inverse Discrete Fourier Transform IE Informationelement IEEE Institute of Electrical and Electronics Engineers IEIInformation Element Identifier IEIDL Information Element Identifier DataLength IMSI International Mobile Subscriber Identity INT-RNTIInterruption RNTI IoT Internet of Things IP Internet Protocol IPsec IPSecurity, Internet Protocol Security IR Infrared IWFInterworking-Function kB Kilobyte (1000 bytes) kbps kilo-bits per secondL1 Layer 1 (physical layer) L1-RSRP Layer 1 reference signal receivedpower L2 Layer 2 (data link layer) L3 Layer 3 (network layer) LAALicensed Assisted Access LAN Local Area Network LBRM Limited Buffer RateMatching LBT Listen Before Talk LDPC Low density parity check LI LayerIndicator LLC Logical Link Control, Low Layer Compatibility LPLMN LocalPLMN LTE Long-Term Evolution LWA LTE-WLAN aggregation LWIP LTE/WLANRadio Level Integration with IPsec Tunnel M2M Machine-to-Machine MACMedium Access Control (protocol layering context) MAC Messageauthentication code (security/encryption context) MAC-A MAC used forauthentication and key agreement (TSG T WG3 context) MAC-I MAC used fordata integrity of signalling messages (TSG T WG3 context) MCS Modulationand Coding Scheme MCS-C-RNTI Modulation and Coding Scheme-Cell-RNTI MeNBmaster eNB MER Message Error Ratio MIB Master Information Block,Management Information Base MM Mobility Management MME MobilityManagement Entity MN Master Node MO Measurement Object, MobileOriginated MPBCH MTC Physical Broadcast CHannel MPDCCH MTC PhysicalDownlink Control CHannel MPDSCH MTC Physical Downlink Shared CHannelMPRACH MTC Physical Random Access CHannel MPUSCH MTC Physical UplinkShared Channel MPLS MultiProtocol Label Switching MTC Machine-TypeCommunications mMTC massive MTC, massive Machine-Type CommunicationsNACK Negative Acknowledgement NAS Non-Access Stratum, Non-Access Stratumlayer NEF Network Exposure Function NF Network Function NG NextGeneration, Next Gen NGEN-DC NG-RAN E-UTRA-NR Dual Connectivity N-PoPNetwork Point of Presence NMIB, N-MIB Narrowband MIB NPBCH NarrowbandPhysical Broadcast CHannel NPDCCH Narrowband Physical Downlink ControlCHannel NPDSCH Narrowband Physical Downlink Shared CHannel NPRACHNarrowband Physical Random Access CHannel NPUSCH Narrowband PhysicalUplink Shared CHannel NPSS Narrowband Primary Synchronization SignalNSSS Narrowband Secondary Synchronization Signal NR New Radio, NeighbourRelation NRF NF Repository Function NW Network NZP Non-Zero Power OFDMOrthogonal Frequency Division Multiplexing OFDMA Orthogonal FrequencyDivision Multiple Access OTA over-the-air P-RNTI Paging RNTI PBCHPhysical Broadcast Channel PCC Primary Component Carrier, Primary CCPCell Primary Cell PCI Physical Cell ID, Physical Cell Identity PCEFPolicy and Charging Enforcement Function PCF Policy Control FunctionPCRF Policy Control and Charging Rules Function PDCP Packet DataConvergence Protocol, Packet Data Convergence Protocol layer PDCCHPhysical Downlink Control Channel PDCP Packet Data Convergence ProtocolPDN Packet Data Network, Public Data Network PDSCH Physical DownlinkShared Channel PDU Protocol Data Unit P-GW PDN Gateway PHICH Physicalhybrid-ARQ indicator channel PHY Physical layer PLMN Public Land MobileNetwork POC PTT over Cellular PP, PTP Point-to-Point PPP Point-to-PointProtocol PRACH Physical RACH PRB Physical resource block PRG Physicalresource block group, Precoding resource block group ProSe ProximityServices, Proximity-Based Service PRS Positioning Reference Signal PSBCHPhysical Sidelink Broadcast Channel PSDCH Physical Sidelink DownlinkChannel PSCCH Physical Sidelink Control Channel PSSCH Physical SidelinkShared Channel PSCell Primary SCell PSS Primary Synchronization SignalPT-RS Phase-tracking reference signal PTT Push-to-Talk PUCCH PhysicalUplink Control Channel PUSCH Physical Uplink Shared Channel QAMQuadrature Amplitude Modulation QCI QoS class of identifier QCL Quasico-location QFI QoS Flow ID, QoS Flow Identifier QoS Quality of ServiceQPSK Quadrature (Quaternary) Phase Shift Keying QZSS Quasi-ZenithSatellite System RA-RNTI Random Access RNTI RAB Radio Access Bearer,Random Access Burst RACH Random Access Channel RADIUS RemoteAuthentication Dial In User Service RAN Radio Access Network RAND RANDomnumber (used for authentication) RAR Random Access Response RAT RadioAccess Technology RAU Routing Area Update RB Resource block, RadioBearer RBG Resource block group REG Resource Element Group RF RadioFrequency RI Rank Indicator RIV Resource indicator value RL Radio LinkRLC Radio Link Control, Radio Link Control layer RLF Radio Link FailureRLM Radio Link Monitoring RLM-RS Reference Signal for RLM RMRegistration Management RMC Reference Measurement Channel RMSI RemainingMSI, Remaining Minimum System Information RN Relay Node RNC RadioNetwork Controller RNL Radio Network Layer RNTI Radio Network TemporaryIdentifier RRC Radio Resource Control, Radio Resource Control layer RRMRadio Resource Management RS Reference Signal RSRP Reference SignalReceived Power RSRQ Reference Signal Received Quality RSSI ReceivedSignal Strength Indicator RSU Road Side Unit RTP Real Time Protocol RTSReady-To-Send RTT Round Trip Time Rx Reception, Receiving, Receiver S1APS1 Application Protocol S1-MME S1 for the control plane S1-U S1 for theuser plane S-GW Serving Gateway S-RNTI SRNC Radio Network TemporaryIdentity S-TMSI SAE Temporary Mobile Station Identifier SCC SecondaryComponent Carrier, Secondary CC SCell Secondary Cell SC-FDMA SingleCarrier Frequency Division Multiple Access SCG Secondary Cell Group SCMSecurity Context Management SCS Subcarrier Spacing SDAP Service DataAdaptation Protocol, Service Data Adaptation Protocol layer SDNFStructured Data Storage Network Function SDSF Structured Data StorageFunction SDU Service Data Unit SEAF Security Anchor Function SeNBsecondary eNB SEPP Security Edge Protection Proxy SFI Slot formatindication SFI-RNTI Slot format indication RNTI SFTD Space-FrequencyTime Diversity, SFN and frame timing difference SFN System Frame NumberSgNB Secondary gNB SGSN Serving GPRS Support Node S-GW Serving GatewaySI System Information SI-RNTI System Information RNTI SIB SystemInformation Block SIM Subscriber Identity Module SIP Session InitiatedProtocol SiP System in Package SL Sidelink SLA Service Level AgreementSLIV Start and Length Indicator SM Session Management SMF SessionManagement Function SMS Short Message Service SMSF SMS Function SMTCSSB-based Measurement Timing Configuration SN Secondary Node, SequenceNumber SoC System on Chip SpCell Special Cell SP-CSI-RNTISemi-Persistent CSI RNTI SPS Semi-Persistent Scheduling SQN Sequencenumber SR Scheduling Request SRB Signalling Radio Bearer SRS SoundingReference Signal SS Synchronization Signal SSB Synchronization SignalBlock, SS/PBCH Block SSBRI SS/PBCH Block Resource Indicator,Synchronization Signal Block Resource Indicator SS-RSRP SynchronizationSignal based Reference Signal Received Power SS-RSRQ SynchronizationSignal based Reference Signal Received Quality SS-SINR SynchronizationSignal based Signal to Noise and Interference Ratio SSS SecondarySynchronization Signal SUL Supplementary Uplink TA Timing Advance,Tracking Area TAC Tracking Area Code TAG Timing Advance Group TAUTracking Area Update TB Transport Block TBS Transport Block Size TBD ToBe Defined TC-RNTI Temporary Cell RNTI TCI Transmission ConfigurationIndicator TCP Transmission Communication Protocol TDD Time DivisionDuplex TDM Time Division Multiplexing TDMA Time Division Multiple AccessTDRA Time Domain Resource Allocation TE Terminal Equipment TEID TunnelEnd Point Identifier TPC Transmit Power Control TPC-PUCCH-RNTI TransmitPower Control-PUCCH-RNTI TPC-PUSCH-RNTI Transmit PowerControl-PUSCH-RNTI TPC-SRS-RNTI Transmit Power Control-SRS-RNTI TPMITransmitted Precoding Matrix Indicator TR Technical Report TRP, TRxPTransmission Reception Point TRS Tracking Reference Signal TRxTransceiver TS Technical Specifications, Technical Standard TTITransmission Time Interval Tx Transmission, Transmitting, TransmitterU-RNTI UTRAN Radio Network Temporary Identity UART UniversalAsynchronous Receiver and Transmitter UCI Uplink Control Information UEUser Equipment UDM Unified Data Management UDP User Datagram ProtocolUDSF Unstructured Data Storage Network Function UICC UniversalIntegrated Circuit Card UL Uplink UL-SCH Uplink Shared Channel UMUnacknowledged Mode UML Unified Modelling Language UMTS Universal MobileTelecommunications System UP User Plane UPF User Plane Function URIUniform Resource Identifier URL Uniform Resource Locator URLLCUltra-Reliable and Low Latency USB Universal Serial Bus USIM UniversalSubscriber Identity Module USS UE-specific search space UTRA UMTSTerrestrial Radio Access UTRAN Universal Terrestrial Radio AccessNetwork V2I Vehicle-to-Infrastruction V2P Vehicle-to-Pedestrian V2VVehicle-to-Vehicle V2X Vehicle-to-everything VoIP Voice-over-IP,Voice-over-Internet Protocol VPLMN Visited Public Land Mobile NetworkWiMAX Worldwide Interoperability for Microwave Access WLAN WirelessLocal Area Network WMAN Wireless Metropolitan Area Network WPAN WirelessPersonal Area Network X2-C X2-Control plane X2-U X2-User plane XMLeXtensible Markup Language XRES EXpected user RESponse XOR eXclusive ORZC Zadoff-Chu

The corresponding structures, material, acts, and equivalents of allmeans or steps plus function elements in the claims below are intendedto include any structure, material or act for performing the function incombination with other claimed elements are specifically claimed. Thedescription of the present disclosure has been presented for purposes ofillustration and description, but is not intended to be exhaustive orlimited to the disclosure in the form disclosed. Many modifications andvariations will be apparent to those of ordinary skill without departingfrom the scope and spirit of the disclosure. The embodiments were chosenand described in order to best explain the principles of the disclosureand the practical application, and to enable others of ordinary skill inthe art to understand the disclosure for embodiments with variousmodifications as are suited to the particular use contemplated.

The foregoing description provides illustration and description ofvarious example embodiments, but is not intended to be exhaustive or tolimit the scope of embodiments to the precise forms disclosed.Modifications and variations are possible in light of the aboveteachings or may be acquired from practice of various embodiments. Wherespecific details are set forth in order to describe example embodimentsof the disclosure, it should be apparent to one skilled in the art thatthe disclosure can be practiced without, or with variation of, thesespecific details. It should be understood, however, that there is nointent to limit the concepts of the present disclosure to the particularforms disclosed, but on the contrary, the intention is to cover allmodifications, equivalents, and alternatives consistent with the presentdisclosure and the appended claims.

1. One or more computer-readable storage media (CRSM) comprisinginstructions, wherein execution of the instructions by one or moreprocessors of a user equipment (UE) is to cause the UE to: determine,based on a time domain resource field of downlink control information(DCI), a starting symbol relative to a start of a slot in which aphysical downlink shared channel (PDSCH) scheduled by the DCI is to bereceived and an allocation length, wherein the allocation length is anumber of consecutive symbols counting from the starting symbol, andwherein a combination of the starting symbol and the allocation lengthis based on a PDSCH mapping type to be assumed for reception of thePDSCH; and control receipt of the PDSCH based on the starting symbol andthe allocation length.
 2. The one or more CRSM of claim 1, wherein thetime domain resource field indicates a row index, and execution of theinstructions is to cause the UE to: identify, in a row corresponding tothe row index, a slot offset, the PDSCH mapping type, a slot offset, anda start and length indicator (SLIV), wherein the SLIV is to indicate thestarting symbol and the allocation length.
 3. The one or more CRSM ofclaim 2, wherein the PDSCH mapping type is either a mapping type A or amapping type B.
 4. The one or more CRSM of claim 3, wherein, when thePDSCH mapping type is the mapping type A, the allocation length is anynumber from three to fourteen, and the starting symbol is one of zero,one, two, or three.
 5. The one or more CRSM of claim 3, wherein, whenthe PDSCH mapping type is the mapping type B, the allocation length iseither two, four, or seven symbols, and the starting symbol is anynumber from zero to twelve.
 6. The one or more CRSM of claim 3, whereinthe combination of the starting symbol and the allocation length is anynumber from three to fourteen when the PDSCH mapping type is the mappingtype A, and the combination of the starting symbol and the allocationlength is any number from two to fourteen when the PDSCH mapping type isthe mapping type B.
 7. The one or more CRSM of claim 2, whereinexecution of the instructions is to cause the UE to: determine theallocation length (L) and the starting symbol (S) from the SLIV,wherein:if (L−1)≤7, then SLIV=14·(L−1)+S, andif (L−1)>7, then SLIV=14·(14−L+1)+(14−1−S), wherein 0<L≤14−S.
 8. The oneor more CRSM of claim 2, wherein execution of the instructions is tocause the UE to: identify, based on a received Radio Resource Control(RRC) message, a time domain allocation list information element (IE)comprising one or more time domain allocation IEs, wherein each timedomain allocation IE of the one or more time domain allocation IEsincludes a slot offset field, a SLIV field, and a mapping type field;and generate a time domain resource allocation table to include one ormore rows corresponding to the one or more time domain allocation IEssuch that each row of the one or more rows includes a corresponding slotoffset field, mapping type field, a starting symbol field and anallocation length field, wherein the starting symbol and the allocationlength fields of each row are based on the SLIV field of a respectivetime domain allocation IE.
 9. The one or more CRSM of claim 1, whereinthe PDSCH is a first PDSCH, the slot is a first slot, the startingsymbol is a first starting symbol, and the allocation length is a firstallocation length, and wherein execution of the instructions is to causethe UE to: determine, based on another time domain resource field ofanother DCI, a second starting symbol relative to a start of a secondslot in which another PDSCH scheduled by the other DCI is to be receivedand a second allocation length, wherein the second allocation length hasa same number of consecutive symbols as the first allocation length, andwherein the second slot is a next consecutive slot in time after thefirst slot without a gap therebetween.
 10. The one or more CRSM of claim1, wherein execution of the instructions is to cause the UE to:determine the combination of the starting symbol and the allocationlength such that the combination of the starting symbol and theallocation length does not cross a slot boundary of the slot.
 11. One ormore computer-readable storage media (CRSM) comprising instructions,wherein execution of the instructions by one or more processors of auser equipment (UE) is to cause the UE to: determine, based on a timedomain resource field of downlink control information (DCI), a startingsymbol relative to a start of a slot in which a physical uplink sharedchannel (PUSCH) scheduled by the DCI is to be transmitted and anallocation length, wherein the allocation length is a number ofconsecutive symbols counting from the starting symbol, and wherein acombination of the starting symbol and the allocation length is based ona PUSCH mapping type to be assumed for the transmission of the PUSCH;and control transmission of the PUSCH based on the starting symbol andthe allocation length.
 12. The one or more CRSM of claim 11, wherein thetime domain resource field indicates a row index, and execution of theinstructions is to cause the UE to: identify, in a row corresponding tothe identified row index, a slot offset, the PUSCH mapping type, a slotoffset, and a start and length indicator (SLIV), wherein the SLIV is toindicate the starting symbol and the allocation length.
 13. The one ormore CRSM of claim 12, wherein the PUSCH mapping type is either amapping type A or a mapping type B.
 14. The one or more CRSM of claim13, wherein, when the PUSCH mapping type is the mapping type A, theallocation length is any number from four to fourteen, and the startingsymbol is zero.
 15. The one or more CRSM of claim 13, wherein, when thePUSCH mapping type is the mapping type B, the allocation length is anynumber from one to fourteen, and the starting symbol is any number fromzero to thirteen.
 16. The one or more CRSM of claim 13, wherein thecombination of the starting symbol and the allocation length is anynumber from three to fourteen when the PUSCH mapping type is the mappingtype A, and the combination of the starting symbol and the allocationlength is any number from two to fourteen when the PUSCH mapping type isthe mapping type B.
 17. The one or more CRSM of claim 12, whereinexecution of the instructions is to cause the UE to: determine theallocation length (L) and the starting symbol (S) from the SLIV,wherein:if (L−1)≤7, then SLIV=14·(L−1)+S, andif (L−1)>7, then SLIV=14·(14−L+1)+(14−1−S), wherein 0<L≤14−S.
 18. Theone or more CRSM of claim 12, wherein execution of the instructions isto cause the UE to: identify, based on a received Radio Resource Control(RRC) message, a time domain allocation list information element (IE)comprising one or more time domain allocation IEs, wherein each timedomain allocation IE of the one or more time domain allocation IEsincludes a slot offset field, a SLIV field, and a mapping type field;and generate a time domain resource allocation table to include one ormore rows corresponding to the one or more time domain allocation IEssuch that each row of the one or more rows includes a corresponding slotoffset field, mapping type field, a starting symbol field and anallocation length field, wherein the starting symbol and the allocationlength fields of each row are based on the SLIV field of a respectivetime domain allocation IE.
 19. The one or more CRSM of claim 11, whereinthe PDSCH is a first PUSCH, the slot is a first slot, the startingsymbol is a first starting symbol, and the allocation length is a firstallocation length, and wherein execution of the instructions is to causethe UE to: determine, based on another time domain resource field ofanother DCI, a second starting symbol relative to a start of a secondslot in which another PUSCH scheduled by the other DCI is to be receivedand a second allocation length, wherein the second allocation length hasa same number of consecutive symbols as the first allocation length, andwherein the second slot is a next consecutive slot in time after thefirst slot without a gap therebetween.
 20. The one or more CRSM of claim11, wherein execution of the instructions is to cause the UE to:determine the combination of the starting symbol and the allocationlength such that the combination of the starting symbol and theallocation length does not cross a slot boundary of the slot.
 21. Anapparatus to be implemented in a Next Generation Radio Access Network(NG-RAN) node, the apparatus comprising: processor circuitry arranged togenerate downlink control information (DCI) to at least include a timedomain resource assignment field, wherein the time domain resourceassignment field is to include a value to indicate a row index of anallocation table, and wherein a row in the allocation tablecorresponding to the row index at least defines a slot offset, a mappingtype, and a start and length indicator (SLIV) or directly a start symboland an allocation length; and interface circuitry coupled with theprocessor circuitry, the interface circuitry arranged to provide the DCIto a radio front end module (RFEM) for transmission to a user equipment(UE).
 22. The apparatus of claim 21, wherein the DCI is to schedule aPhysical Downlink Shared Channel (PDSCH), the mapping type is a PDSCHmapping type to be assumed for reception of the PDSCH, the PDSCH mappingtype is either a PDSCH mapping type A or a PDSCH mapping type B, andwherein: when the PDSCH mapping type is the mapping type A, theallocation length is any number from three to fourteen, and the startingsymbol is one of zero, one, two, or three; and when the PDSCH mappingtype is the mapping type B, the allocation length is either two, four,or seven symbols, and the starting symbol is any number from zero totwelve.
 23. The apparatus of claim 21, wherein the DCI is to schedule aPhysical Uplink Shared Channel (PUSCH), the mapping type is a PUSCHmapping type to be assumed for transmission of the PUSCH, the PUSCHmapping type is either a PUSCH mapping type A or a PUSCH mapping type B,and wherein: when the PUSCH mapping type is the mapping type A, theallocation length is any number from four to fourteen, and the startingsymbol is zero; and when the PUSCH mapping type is the mapping type B,the allocation length is any number from one to fourteen, and thestarting symbol is any number from zero to thirteen.
 24. The apparatusof claim 21, wherein: the processor circuitry is arranged to generate aRadio Resource Control (RRC) message to include a configuration, whereinthe configuration is to include a time domain allocation list(TimeDomainAllocationList) information element (IE), wherein theTimeDomainAllocationList IE includes one or more time domain allocation(TimeDomainAllocation) IEs, wherein each TimeDomainAllocation IE of theone or more TimeDomainAllocation IEs is to correspond to a row in theallocation table; and the interface circuitry arranged to provide theRRC message to the RFEM for transmission to the UE prior to transmissionof the DCI.
 25. The apparatus of claim 21, wherein: the processorcircuitry is arranged to generate an RRC message to include aconfiguration, wherein the configuration is to not include aTimeDomainAllocationList IE to indicate to use a default allocationtable based on a type of Radio Network Temporary Identifier (RNTI) to beincluded with a transmission scheduled by the DCI; and the interfacecircuitry arranged to provide the RRC message to the RFEM fortransmission to the UE prior to transmission of the DCI.